- Remove the dependency on @types/react (@Vinnl)
- Support React 16 and Enzyme 3 (@blainekasten)
- Remove beforeEnter call for jest-enzyme and just add the matchers once. (@mockdeep)
- Fix missing flow annotation that caused issues with flow 0.54. (@fabiob)
- Fix flow issues that cropped up from 3.8.1. (@blainekasten)
- Fix a bug that prevents this library from working with Jest 21+. (@nigelzor)
- Intentionally passing undefined to toHaveState and toHaveProps now compares on the undefined value. (@DianaSuvorova)
- Fix pretty printing Proxy objects in components (@chris-divvito)
- Fix negative messages in jasmine-enzyme (@blainekasten)
- Address some internal issues that broke tests in CI (@blainekasten)
- Fix a bad publish with 3.6.0 not including all documented changes
- Implement jest asymettric matchers and jasmine partial matchers!! (@sfargier)
- This means you can use API's like
expect.any(String)
in jest orjasmine.stringMatching('%')
- This means you can use API's like
- Fix a bug with the transpiled code not runnable in browsers (@ek5000)
- Make the typescript definition for jest-enzyme more accurate (@sfargier)
- internal: enzyme-matchers is built in Prettier now! (@blainekasten)
- internal: Fix a local issue with our yarn.lock (@blainekasten)
- Point to lib TS file (@pascalduez)
- Add the missing export of the toMatchElement assertion (@vkrol)
- Fix the TS definition for
toContainReact
(@pselden)
- Include TS definitions in exported library (@Dean177)
- Fix a bug that can occur when you are mocking console.error in your tests. (@juanca)
- [internal] Use babel-preset-env (@pascalduez)
- [internal] Improve flowtype usage (@pascalduez)
- Add toMatchElement TS Declaration (@pascalduez)
- Prevented
toHaveProps
from mutating arguments (@moredip) - Ensure flowtypes are published as part of the packages (@pascalduez)
- Fix typescript return types (@Dean177)
- Fix Flowtype integration by not publishing
src/
files (@SBoudrias) - NEW! Added
toMatchElement(reactInstance)
matcher (@finnigantime)
- Publish types for Flow integration support
- Fix an issue where
console
may not be available in certain environments - Expose matchers directly for
jasmine-enzyme
- This is particularily benefecial for jasmine v1 users
- Access if found at
jasmineEnzyme.enzymeMatchers
- Fix an issue with using shallow wrappers when running tests in IE
- Fix a bug when running tests in IE
- Add Typescript definitions
- Fix a failed version publish
- This version updates the requirement for jest-enzyme to jest versions 19 or greater
- Automatically inject a serializer for enzyme components to be snapshotted
- Bugfix: Prevent shallow wrappers from being deeply rendered by our internal
html
utils
- Remove dependency on colors package
- Fix stringify to not crash on
null
values
- Fix the way we looked up internals of react for latest version
- Fix matcher messages from always sounding positive, even when negated
-
Changed project structure!
-
We are now using lerna to maintain 3 npm packages:
enzyme-matchers
(simple functions to handle assertions)jasmine-enzyme
(implementation of enzyme-matchers in jasmine)jest-enzyme
(_implementation of enzyme-matchers in jest)
-
This is only breaking if you use Jest.
- If you do, simply change to use the
jest-enzyme
package and everything should work.
- If you do, simply change to use the
- Fixed negated matchers output message to sound negated.
- Add
toHaveText
matcher
- Include
repository
in package.json
- Rename
toContain
totoContainReact
to prevent core matcher overwrite - Rename
toMatch
totoMatchSelector
to prevent core matcher overwrite
- Remove
jasmine
from thepeerDependencies
list- Jasmine is implicity with the library
- the peerDep caused issues with npm2 and jest
0.2.1 was a failed release
- Fix flowtype issues
- Add
toHaveStyle
matcher
- Initial Implementation