-
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
[canvas] migrate tests away from karma #73121
Conversation
]); | ||
expect(newState.resolvedArgs['element-1']).toMatchInlineSnapshot(` | ||
Object { | ||
"0": Object { |
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.
This is the return value produced by resolvedArgsReducer()
which used to work by the check that .to.eql()
ran. Jest assertions are a bit more picky (in a good way, the return value shouldn't eql an array) but I just wanted to raise awareness a little... this is weirdness
Pinging @elastic/kibana-canvas (Team:Canvas) |
Thanks for doing this. Checked the storyshots and tests... all looks good! FYI: the removed storyshot is due to a PR I merged that prevents Redux-based Storybook stories from being 'shotted. |
@elasticmachine merge upstream |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
Co-authored-by: spalger <spalger@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
To get closer to being able to stop using Karma we need to move canvas tests that are using Karma to use Jest instead.
Most tests moved over pretty easy, a couple places made sense to switch to TS quickly.