Jest utilities for Styled Components
``sh`
yarn add --dev jest-styled-components
`js
import React from 'react'
import styled from 'styled-components'
import renderer from 'react-test-renderer'
import 'jest-styled-components'
const Button = styled.button
color: red;
test('it works', () => {
const tree = renderer.create().toJSON()
expect(tree).toMatchSnapshot()
expect(tree).toHaveStyleRule('color', 'red')
})
`
If you don't want to import the library in every test file, it's recommended to use the global installation method.
Table of Contents
=================
* Snapshot Testing
* Enzyme
* react-testing-library
* Theming
* Preact
* Serializer
* toHaveStyleRule
* Global installation
* Working with multiple packages
* Contributing
Jest snapshot testing is an excellent way to test React components (or any serializable value) and make sure things don't change unexpectedly.
It works with Styled Components but there are a few problems that this package addresses and solves.
For example, suppose we create this styled Button:
`js
import styled from 'styled-components'
const Button = styled.button
color: red;
Which we cover with the following test:
`js
import React from 'react'
import renderer from 'react-test-renderer'
test('it works', () => {
const tree = renderer.create().toJSON()
expect(tree).toMatchSnapshot()
})
`
When we run our test command, Jest generates a snapshot containing a few class names (which we didn't set) and no information about the style rules:
`jsit works 1
exports[] =
/>;`
Consequently, changing the color to green:
`js
const Button = styled.button
color: green;
Results in the following diff, where Jest can only tell us that the class names are changed.
Although we can assume that if the class names are changed the style rules are also changed, this is not optimal (and is not always true).
`diff
- Snapshot
+ Received
+ className="sc-bdVaJa hUzqNt"
/>
`
Here's where Jest Styled Components comes to rescue.
We import the package into our test file:
`js`
import 'jest-styled-components'
When we rerun the test, the output is different: the style rules are included in the snapshot, and the hashed class names are substituted with placeholders that make the diffs less noisy:
`diff
- Snapshot
+ Received
+.c0 {
+ color: green;
+}
+
+ className="c0"
/>
`
This is the resulting snapshot:
`jsit works 1
exports[] =
.c0 {
color: green;
}
/>;`
Now, suppose we change the color again to blue:
`js
const Button = styled.button
color: blue;
Thanks to Jest Styled Components, Jest is now able to provide the exact information and make our testing experience even more delightful 💖:
`diff
- Snapshot
+ Received
.c0 {
- color: green;
+ color: blue;
}
/>
`
enzyme-to-json is necessary to generate snapshots using Enzyme's shallow or full DOM rendering.
`sh`
yarn add --dev enzyme-to-json
It can be enabled globally in the package.json:
`js`
"jest": {
"snapshotSerializers": [
"enzyme-to-json/serializer"
]
}
Or imported in each test:
`js
import toJson from 'enzyme-to-json'
// ...
expect(toJson(wrapper)).toMatchSnapshot()
`
Jest Styled Components works with shallow rendering:
`js
import { shallow } from 'enzyme'
test('it works', () => {
const wrapper = shallow()
expect(wrapper).toMatchSnapshot()
})
`
And full DOM rendering as well:
`js
import { mount } from 'enzyme'
test('it works', () => {
const wrapper = mount()
expect(wrapper).toMatchSnapshot()
})
`
To generate snapshots with react-testing-library, you can follow the example below:
`js
import { render } from '@testing-library/react'
test('it works', () => {
const { container } = render()
expect(container.firstChild).toMatchSnapshot()
})
`
> The snapshots will contain class instead of className because the snapshots are of DOM elements
In some scenarios, testing components that depend on a theme can be tricky,
especially when using Enzyme's shallow rendering.
For example:
`js
const Button = styled.button
color: ${props => props.theme.main};
const theme = {
main: 'mediumseagreen',
}
`
The recommended solution is to pass the theme as a prop:
`js`
const wrapper = shallow()
The following function might also help for shallow rendering:
`js
const shallowWithTheme = (tree, theme) => {
const context = shallow(
.instance()
.getChildContext()
return shallow(tree, { context })
}
const wrapper = shallowWithTheme(, theme)
`
and for full DOM rendering:
`js
const mountWithTheme = (tree, theme) => {
const context = shallow(
.instance()
.getChildContext()
return mount(tree, {
context,
childContextTypes: ThemeProvider.childContextTypes,
})
}
`
To generate snapshots of Preact components,
add the following configuration:
`js`
"jest": {
"moduleNameMapper": {
"^react$": "preact-compat"
}
}
And render the components with preact-render-to-json:
`js
import React from 'react'
import styled from 'styled-components'
import render from 'preact-render-to-json'
import 'jest-styled-components'
const Button = styled.button
color: red;
test('it works', () => {
const tree = render()
expect(tree).toMatchSnapshot()
})
`
> The snapshots will contain class instead of className.
Learn more.
The serializer can be imported separately from jest-styled-components/serializer.
This makes it possible to use this package with specific-snapshot and other libraries.
`js
import React from 'react'
import styled from 'styled-components'
import renderer from 'react-test-renderer'
import { styleSheetSerializer } from "jest-styled-components/serializer"
import { addSerializer } from "jest-specific-snapshot"
addSerializer(styleSheetSerializer)
const Button = styled.button
color: red;
test('it works', () => {
const tree = renderer.create().toJSON()
expect(tree).toMatchSpecificSnapshot("./Button.snap")
})
`
The serializer can be configured to control the snapshot output.
`js
import { render } from '@testing-library/react'
import { setStyleSheetSerializerOptions } from 'jest-styled-components/serializer'
setStyleSheetSerializerOptions({
addStyles: false,
classNameFormatter: (index) => styled${index}
});
test('it works', () => {
const { container } = render()
expect(container.firstChild).toMatchSnapshot()
})
`
The toHaveStyleRule matcher is useful to test if a given rule is applied to a component.undefined
The first argument is the expected property, the second is the expected value which can be a String, RegExp, Jest asymmetric matcher or .
When used with a negated ".not" modifier the second argument is optional and can be omitted.
`js
const Button = styled.button
color: red;
border: 0.05em solid ${props => props.transparent ? 'transparent' : 'black'};
cursor: ${props => !props.disabled && 'pointer'};
opacity: ${props => props.disabled && '.65'};
test('it applies default styles', () => {
const tree = renderer.create().toJSON()
expect(tree).toHaveStyleRule('color', 'red')
expect(tree).toHaveStyleRule('border', '0.05em solid black')
expect(tree).toHaveStyleRule('cursor', 'pointer')
expect(tree).not.toHaveStyleRule('opacity') // equivalent of the following two
expect(tree).not.toHaveStyleRule('opacity', expect.any(String))
expect(tree).toHaveStyleRule('opacity', undefined)
})
test('it applies styles according to passed props', () => {
const tree = renderer.create().toJSON()
expect(tree).toHaveStyleRule('border', expect.stringContaining('transparent'))
expect(tree).toHaveStyleRule('cursor', undefined)
expect(tree).toHaveStyleRule('opacity', '.65')
})
`
The matcher supports an optional third options parameter which makes it possible to search for rules nested within an At-rule (see media and supports) or to add modifiers to the class selector. This feature is supported in React only, and more options are coming soon.
`js
const Button = styled.button
@media (max-width: 640px) {
&:hover {
color: red;
}
}
test('it works', () => {
const tree = renderer.create().toJSON()
expect(tree).toHaveStyleRule('color', 'red', {
media: '(max-width:640px)',
modifier: ':hover',
})
})
`
If a rule is nested within another styled-component, the modifier option can be used with the css helper to target the nested rule.
`js
const Button = styled.button
color: red;
const ButtonList = styled.div
display: flex;
${Button} {
flex: 1 0 auto;
}
import { css } from 'styled-components';
test('nested buttons are flexed', () => {
const tree = renderer.create(
expect(tree).toHaveStyleRule('flex', '1 0 auto', {
modifier: css${Button},`
})
})
You can take a similar approach when you have classNames that override styles
`js
const Button = styled.button
background-color: red;
&.override {
background-color: blue;
}
const wrapper = mount();
expect(wrapper).toHaveStyleRule('background-color', 'blue', {
modifier: '&.override',
});
`
This matcher works with trees serialized with react-test-renderer, react-testing-library, or those shallow rendered or mounted with Enzyme.
It checks the style rules applied to the root component it receives, therefore to make assertions on components further in the tree they must be provided separately (Enzyme's find might help).
> Note: for react-testing-library, you'll need to pass the first child to check the top-level component's style. To check the styles of deeper components, you can use one of the getBy* methods to find the element (e.g. expect(getByTestId('styled-button')).toHaveStyleRule('color', 'blue'))
To use the toHaveStyleRule matcher with React Native, change the import statement to:
`js`
import 'jest-styled-components/native'
It is possible to setup this package for all the tests. For Example: import the library once in the src/setupTests.js as follows:
`js`
import 'jest-styled-components'
...then add the following to test.config.js:
`js`
setupFilesAfterEnv: ['
If Jest Styled Components is not working, it is likely caused by loading multiple instances of styled-components. This can happen especially when working with a Lerna monorepo. Starting with styled-components@3.2.0, a warning will be logged when multiple instances of it are being included and run as part of the Jest tests. Using styled-components@3.1.6 and lower with multiple instances will cause a silent error with unexpected results.
To debug and fix multiple instances of styled-components` see the FAQ on "Why am I getting a warning about several instances of module on the page?".
Please open an issue and discuss with us before submitting a PR.