Use EUI test environment build with Jest#55877
Conversation
|
Pinging @elastic/kibana-design (Team:Design) |
|
Update: We released the new test build as part of eui@19.0.0 this week. Once Kibana has been updated to use that version, I will update this PR to have more clear intentions. |
|
Snapshot test failures are as expected. I'll be updating snapshots next week to match new expected output for |
|
Waiting on a resolution to #58068 before this can move forward |
spalger
left a comment
There was a problem hiding this comment.
The jest changes here look fine, but the large number of changed snapshots is concerning... Are there multiple changes we could decouple a bit? Why does this change to the config cause so many snapshots to update?
legrego
left a comment
There was a problem hiding this comment.
Love it! Security changes LGTM
chrisronline
left a comment
There was a problem hiding this comment.
Stack monitoring changes LGTM!
lizozom
left a comment
There was a problem hiding this comment.
@elastic/kibana-app-arch changes are only snapshots.
LGTM
pgayvallet
left a comment
There was a problem hiding this comment.
LGTM for platform changes
kertal
left a comment
There was a problem hiding this comment.
LGTM for KibanaApp, 👍 for this Kibana snapshot diet
chandlerprall
left a comment
There was a problem hiding this comment.
Changes LGTM; jest configuration looks correct, and the changes to tests' selectors and their snapshots look like what we expect
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
* wip * dir name * src snapshot changes * x-pack snapshots * svg element lookups * snapshot updates Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Use EUI test environment build with Jest (#55877) * wip * dir name * src snapshot changes * x-pack snapshots * svg element lookups * snapshot updates Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> * yarn.lock update Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* master: [ML] Transforms: Use EuiInMemoryTable instead of custom typed table. (elastic#59782) Alerting/fix flaky instance test (elastic#58994) ci: disable all Mocha rules for tape tests (elastic#59798) Fix UX in alerting UI forms when errors occur (elastic#59444) [DOCS] Updated and added jump tables (elastic#59774) [DOCS] Moved rolled up index content (elastic#59372) Regenerate core api docs (elastic#59814) [Lens] remove react warnings (elastic#59574) The scripts/backport.js file isn't an executable (elastic#59800) [Alerting] add more alert properties to action parameter templating (elastic#59718) [Design] Branding changes in Elastic to focus more towards the Elastic brand (elastic#58160) [SIEM] Adds 'Create new rule' Cypress test (elastic#59790) Updating svgo -> css-tree -> mdn-data, all so we get mdn-data > 2.0 (elastic#58913) Use EUI test environment build with Jest (elastic#55877) update typescript version in all packages to avoid warnings (elastic#59787) [SIEM] [Case] Insert timeline into case textarea (elastic#59586) [ML] Functional tests - stabilize saved search tests (elastic#59652)
Summary
Set Jest's
moduleNameMapperconfig to use EUI's new commonjs test environment build. This build has async & dynamic import functions transformed, removing the need for Kibana to do so. We've also mocked theEuiIconcomponent to solidify snapshot testing output. Instead of the fullsvgicon, snapshots will now get adivwith relevant identifying attributes.Sibling/dependent PR: elastic/eui#2698Undoes the Jest environment changes introduced in #36316 when EUI started using dynamic imports.
Checklist
- [ ] This was checked for cross-browser compatibility, including a check against IE11- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support- [ ] Documentation was added for features that require explanation or tutorials- [ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers
- [ ] This includes a feature addition or change that requires a release note and was labeled appropriately