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
chore(tests): setup circleci to run unit tests againt v5 #36714
Conversation
// The second param is a "hint", see: https://jestjs.io/docs/en/expect#tomatchsnapshotpropertymatchers-hint | ||
expect(results).toMatchSnapshot({}, `results`) | ||
expect(reporter.warn.mock.calls).toMatchSnapshot({}, `warn`) | ||
expect(reporter.panicOnBuild.mock.calls).toMatchSnapshot({}, `panicOnBuild`) | ||
expect({ | ||
results, | ||
warnCalls: reporter.warn.mock.calls, | ||
panicOnBuildCalls: reporter.panicOnBuild.mock.calls, | ||
}).toMatchSnapshot() |
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 was failing with "obsolete snapshots" even tho jest is supposed to not fail on it when there are snapshots in skipped tests ( jestjs/jest#3038 ). Seems like either using multiple snapshots and/or using the named ones is edge case, so I used single snapshot here instead
postfix: `SortInputProp2`, | ||
postfix: `SortInput`, |
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 actual v5 code fix that slipped through original PR ( #36708 )
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.
Description
Documentation
Related Issues