Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

[INFRA] Reduce the number of GitHub job runs for e2e tests #3196

Open
tbouffard opened this issue Oct 21, 2024 · 0 comments
Open

[INFRA] Reduce the number of GitHub job runs for e2e tests #3196

tbouffard opened this issue Oct 21, 2024 · 0 comments
Labels
chore Build, CI/CD or repository tasks (issues/PR maintenance, environments, ...)

Comments

@tbouffard
Copy link
Member

First improvements were done with #2172 that already improve the situation a lot.

Detection of Dependencies change

We could reduce the number of e2e tests run when some dependencies are updated.

Currently, we run the tests each time the package.json changes. When a production dependency changes, we must run the tests.
But, there are a few development dependencies that impact the e2e tests (jest, ts-jest, playwright and probably others). Can we skip running the tests when non related dependencies change?

https://github.com/tj-actions/changed-files let get the list of changed files and detect if package.json and package-lock.json are the sole changed files in the PR.
The code of https://github.com/MontyD/package-json-updated-action could be use to retrieve the previous and current version of the files and perform the diff.

Tested browsers

Do we need to test all browsers with all OS every time?

@tbouffard tbouffard added the chore Build, CI/CD or repository tasks (issues/PR maintenance, environments, ...) label Oct 21, 2024
@tbouffard tbouffard added this to the Development Impediments milestone Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Build, CI/CD or repository tasks (issues/PR maintenance, environments, ...)
Projects
None yet
Development

No branches or pull requests

1 participant