-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Updates to Jest configuration #125727
Updates to Jest configuration #125727
Conversation
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
💚 Build SucceededMetrics [docs]
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-operations (Team:Operations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked that node scripts/jest_integration
works, looks like all 208 Jest Unit configs and all 14 Integration configs are still running 👍
(cherry picked from commit e9d82d1)
💔 Some backports could not be created
How to fixRe-run the backport manually:
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit e9d82d1) # Conflicts: # .buildkite/scripts/steps/code_coverage/jest.sh
(cherry picked from commit e9d82d1) # Conflicts: # .buildkite/scripts/steps/code_coverage/jest.sh
Removes the root Jest configurations from the repository as it's are no longer needed after #125454. The root configuration should not be used as loading the entire project is too slow.
yarn test:jest {path}
ornode scripts/jest {path}
should be used instead. Or, you can pass ajest.config.js
file directory toyarn jest
or./node_modules/.bin/jest
.Additionally:
node scripts/check_jest_configs
doesn't exit with a non-zero exit code when a configuration file is missing.scripts/jest_functional