Security News
New Proposed CISA Mandate Would Require Critical Infrastructure to Report Ransom Payments Within 24 Hours
CISA has proposed a set of new rules that would require critical infrastructure to report cyber incidents and ransom payments.
enzyme-to-json
Advanced tools
convert enzyme wrapper to a format compatible with Jest snapshot
Weekly downloads
Readme
Convert Enzyme wrappers to a format compatible with Jest snapshot testing.
$ npm install --save-dev enzyme-to-json
The serializer is the recommended way to use enzyme-to-json
, the installation and usage of it is very easy and allows you to write clean and simple snapshot tests.
In order to use the serializer, just add this line to your Jest configuration:
"snapshotSerializers": ["enzyme-to-json/serializer"]
For most projects, that is all you need to start using snapshot tests on Enzyme wrappers. The rest of this readme is only showing advanced usages of this library.
In case you are still confused, here is a minimal example project demonstrating this configuration.
You can add the serializer for only one Jest test file by adding these lines at the beginning of your Jest unit test file:
import {createSerializer} from 'enzyme-to-json';
expect.addSnapshotSerializer(createSerializer({mode: 'deep'}));
You can also add the serializer for all tests using the setupFilesAfterEnv
configuration option from Jest.
At the beginning, enzyme-to-json
was just a helper because serializers weren't supported by Jest. Even though it is now recommended to use the serializer to keep your tests simple, you can still use the helper as it gives you access to the option objects.
The helper is just a function you can import from enzyme-to-json
and just pass your Enzyme wrapper as the first parameter and snapshot test the returned value, you'll get the same results as if you used the serializer. Note that you don't have to disable the serializer if you had configured it for the rest of your project. Here is a usage example:
import React, {Component} from 'react';
import {shallow} from 'enzyme';
import toJson from 'enzyme-to-json';
it('renders correctly', () => {
const wrapper = shallow(
<MyComponent className="my-component">
<strong>Hello World!</strong>
</MyComponent>,
);
expect(toJson(wrapper)).toMatchSnapshot();
});
The main purpose of using the helper is to use the option object. The option object is just the second argument of the helper, here is an example:
toJson(wrapper, {
noKey: false,
mode: 'deep',
});
And here are all the possible options:
Key | Value | Description |
---|---|---|
noKey | bool | Since v2.0.0 , the key prop is included in the snapshot, you can turn it off if you don't want your key to be in your snapshot by settting this option to true . Only works for the mount and shallow wrappers. |
mode | 'deep' , 'shallow' | The deep option will return a test object rendered to maximum depth while the shallow option will return a test object rendered to minimum depth. Only works for the mount wrappers. See mode documentation for examples. |
map | function | You can change each nested node of your component output by providing the map option. See map documentation for examples. |
ignoreDefaultProps | bool | You can exclude the default props from snapshots in shallow mode |
FAQs
convert enzyme wrapper to a format compatible with Jest snapshot
The npm package enzyme-to-json receives a total of 676,345 weekly downloads. As such, enzyme-to-json popularity was classified as popular.
We found that enzyme-to-json demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISA has proposed a set of new rules that would require critical infrastructure to report cyber incidents and ransom payments.
Security News
Redis is no longer OSS, breaking its explicit commitment to remain under the BSD 3-Clause License forever. This has angered contributors who are now working to fork the software.
Product
Socket AI now enables 'AI detected potential malware' alerts by default, ensuring users benefit from AI-powered state-of-the-art malware detection without needing to opt-in.