chore: Remove repetition of matcherName and options in matchers #8224
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Follow example of snapshot matchers in #8132
This pattern reduces chance of mistakes in remaining improvements to matchers
For example, when in this pull request I cut one of the existing literal objects for options in
toBe
and forgot to replaceisNot: true
withisNot: this.isNot
until it broke some e2e testsAlso:
diffString
withdifference
because it isn’t always a stringnull
with''
forsecondArgument
intoHaveProperty
and removed 3 occurrencesas MatcherHintOptions
matcherHint
call intoStrictEqual
to call function only when test failsTest plan
Updated snapshots in
matchers.test.ts
fornot
in regular black instead of dim:.not.toHaveProperty
.not.toMatchObject
The matcher name in hint remains dim as clue that their reports are not yet improved.
Removed
'proxies matchers to expect'
test according to #7970 (comment)packages/jest-jasmine2/src/__tests__/matchers.test.ts
packages/jest-jasmine2/src/__tests__/__snapshots__/matchers.test.ts.snap