This website requires JavaScript.
Explore
Help
Sign In
archive
/
rsnext
Watch
1
Star
0
Fork
You've already forked rsnext
0
Code
Issues
Pull requests
Projects
Releases
Packages
Wiki
Activity
Actions
978af08cc4
rsnext
/
test
/
related-tests-manifest.json
4 lines
85 B
JSON
Raw
Normal View
History
Unescape
Escape
chore: add test mapping script (#63757) ### What? This adds a script that first gets a list of changed files compared to our base branch (`canary`) in PRs and identifies related test files by looking them up from a `related-tests-manifest.json`, then runs them. ### Why? We would like to be able to run related E2E tests when certain files change, so we can test deployment stability. NOTE: We still want to run all E2E tests on PRs, but this script can be used to also test deployments for hot paths. Since these tests can take up to [3-4 hours](https://github.com/vercel/next.js/actions/workflows/test_e2e_deploy.yml), we aim to run a subset of these tests first. Closes NEXT-2947
2024-04-11 09:44:47 +02:00
{
Reapply "chore(test): run related E2E deploy tests on PRs" (#64682) (#64712)
2024-04-19 11:02:43 +02:00
"packages/next/src/server"
:
[
"e2e/app-dir/ppr-full"
,
"e2e/app-dir/ppr-errors"
]
chore: add test mapping script (#63757) ### What? This adds a script that first gets a list of changed files compared to our base branch (`canary`) in PRs and identifies related test files by looking them up from a `related-tests-manifest.json`, then runs them. ### Why? We would like to be able to run related E2E tests when certain files change, so we can test deployment stability. NOTE: We still want to run all E2E tests on PRs, but this script can be used to also test deployments for hot paths. Since these tests can take up to [3-4 hours](https://github.com/vercel/next.js/actions/workflows/test_e2e_deploy.yml), we aim to run a subset of these tests first. Closes NEXT-2947
2024-04-11 09:44:47 +02:00
}
Reference in a new issue
Copy permalink