-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[jest] Support meta project configs #118122
Conversation
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Pinging @elastic/kibana-operations (Team:Operations) |
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
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.
Thank you @tylersmalley for adding this. Much appreciated 💙
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Friendly reminder: Looks like this PR hasn’t been backported yet. |
2 similar comments
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
In #117188 we had to split up the security solution Jest configs quite a bit until we work out the memory leaks and are able to shard configs based on history build times.
One problem raised is there is no longer an easy way to run all tests under the security solution plugin. This PR should address that by adding a dev Jest config.
You can run it manually with
node ./node_modules/.bin/jest --config x-pack/plugins/security_solution/jest.config.dev.js
Or, with
yarn test:jest x-pack/plugins/security_solution