< UNDEFINED NULL />

React TDD Example: Unit Testing and Building a React Component with Jest, Gulp and React Test Utils

3 May 2015
About 7 min read
React Jest TDD

ReactJs has attained lot of momentum since its initial release in 2013, and became the best JavaScript library for developing rich UI interface. React also popularized different concepts like Virtual DOM, Uni-directional data flow and Componentization in the front-end community. As of today, React has more than 20,000 stars in Github repo, and actively maintained by the Facebook team.

Update Feb 9 2016 : The ReactJS version is bumped to 0.14 in the seed project and updated the article accordingly.

React and Jest for TDD

As I said already, React is a solid piece of work from Facebook. Any solid software will be built with testability in mind; And React is not an exception to that. Facebook built React with complete testing support -- They even released their own testing framework named "Jest" and React Test Utils for unit testing React components.

Here in this post, we'll see how to build a react component in TDD approach.

What we're going to build ?

We will build a simple Accordion component in React. If you're not sure what an Accordion is, have a look at the twitter bootstrap page:

Accordion Widget
Or, see
jQuery UI Accordion

We'll be creating a simple Accordion component in React.

Setting up the tools

We're going to build our component in TDD fashion. Hence, we need to set up our environment with a test runner (for running unit tests), and local server ( with automatic reloading enabled ).

These are the tools I am going to use:

  1. BrowserSync for live development ( browser reloading ).
  2. Jest for unit testing.
  3. JSPM and npm for package management.
  4. Gulp for running build and test tasks.
  5. Finally, ReactJS for developing our component

Setting up all these takes time. Therefore, I have created a seed project for bootstrapping the set-up and the initial boiler plate code. So, as the first step, clone the seed project to your system:

git clone git@github.com:shidhincr/react-jest-gulp-jspm-seed.git react-seed
cd react-seed
npm install

Once you download the seed and install the node modules, we're good to start.

Developing the Component in TDD

We're using Gulp as our build and task tool. If you open the gulpfile.js in the seed folder, you can see there are two main tasks for test driven development ( as explained in the project README file ). One task will build the project and open the development server in browser, while the other task run the unit tests and watch for any changes the source files and test files.

Open two terminal windows, and run gulp develop in one and gulp test in the other one.

There are two example files provided in the scripts folder and __tests__ folder. When you run the gulp test task at first, you should see those tests passing.

Accordion React Component

Let's add the file accordionComponent.js in scripts and accordionComponent-spec.js in the __tests__ folders respectively.

From here onwards, we're going to build our component by writing each functionality as a test case and then implementing them. When adding the test case, you should be able to see the tests failing in the terminal ( gulp test ). Hence, once we see the failing test, the next step is to implement the code to make them pass.

Test Case 1:

The accordion should exist as a React Component

Write the first test case in accordionComponent-spec.js

jest.dontMock('../scripts/accordionComponent.js');

describe('Accordion', function() {
var React = require('react');
var ReactDOM = require('react-dom');
var TestUtils = require('react-addons-test-utils');

var Accordion;

beforeEach(function() {
Accordion = require('../scripts/accordionComponent');
});

it('should exists', function() {
// Render into document
var accordion = TestUtils.renderIntoDocument( <Accordion /> );
expect(TestUtils.isCompositeComponent(accordion)).toBeTruthy();
});
});
Note: By using jest.dontMock, we get the original react component in the scripts folder ( as Jest tries to mock every component by default ).

Let's make the test pass:

'use strict';

var React = require('react');

var Accordion = React.createClass({
render: function(){
return (
<div>Accordion component</div>
);
}
});

module.exports = Accordion;

Okay, the tests are passing now. Let's also make sure that our component renders properly in the browser. Modify the app.js to render the accordionComponent.

'use strict';

var React = require('react');
var ReactDOM = require('react-dom');
var Accordion = require('components/accordionComponent');
ReactDOM.render(<Accordion/>, document.getElementById('view'));

If it works, proceed to next test case.

Test Case 2:

Accordion should build the layout from an array of objects passed as prop.

This time let's make our component configurable. We have to pass an array data to the component, and expect it to build the layout for the Accordion.

it('should build the layout from an array of objects passed as prop', function() {

var input = [{
name: 'Title 1',
content: 'Content belongs to title 1'
},{
name: 'Title 2',
content: 'Content belongs to title 2'
}];

var accordion = TestUtils.renderIntoDocument( <Accordion data={input}/> );
var headers = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-header');
var contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');

expect(headers.length).toEqual(2);
expect(contents.length).toEqual(2);

expect(headers[0].textContent).toEqual('Title 1');
expect(headers[1].textContent).toEqual('Title 2');

expect(contents[0].textContent).toEqual('Content belongs to title 1');
expect(contents[1].textContent).toEqual('Content belongs to title 2');
});

To make everything green:

'use strict';

var React = require('react');

var Accordion = React.createClass({
render: function(){
var panes = [];
var data = this.props.data || [];

data.forEach(function(item, index){
panes.push(
<div key={index}>
<div className="accordion-header">
{item.name}
</div>
<div className="accordion-content">
{item.content}
</div>
</div>
);
});

return (
<div className="accordion">
{panes}
</div>
);
}
});

module.exports = Accordion;

All the tests pass now. To see the component works in browser, edit the app.js and pass the configuration:

'use strict';

var React = require('react');
var ReactDOM = require('react-dom');
var Accordion = require('components/accordionComponent');
var input = [{
name: 'Title 1',
content: 'Content belongs to title 1'
},{
name: 'Title 2',
content: 'Content belongs to title 2'
}];

ReactDOM.render(<Accordion data={input}/>, document.getElementById('view'));

You should be able to see that our Accordion component renders the new layout.

Test Case 3:

By default, all the content section should be hidden unless specified by a flag.

Add the following test case:

it('should hide all the contents by default unless specified by a flag', function(){
var input = [{
name: 'Title 1',
content: 'Content belongs to title 1'
},{
name: 'Title 2',
content: 'Content belongs to title 2',
showOnLoad: true
}];

var accordion = TestUtils.renderIntoDocument( <Accordion data={input}/> );
var contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');
expect(contents.length).toEqual(1);
expect(contents[0].textContent).toEqual('Content belongs to title 2');
});

And make it pass:

'use strict';

var React = require('react');

var Accordion = React.createClass({
render: function(){
var panes = [];
var data = this.props.data || [];

var getContent = function(item){
return !item.showOnLoad ? '': (
<div className="accordion-content">
{item.content}
</div>
);
};

data.forEach(function(item, index){
panes.push(
<div key={index}>
<div className="accordion-header">
{item.name}
</div>
{ getContent(item) }
</div>
);
});

return (
<div className="accordion">
{panes}
</div>
);
}
});

module.exports = Accordion;

This code will make the above test case pass, but you can see that it makes the previous test case ( Test case 2 ) fail.

This is not a problem at all, because in TDD this is what we expect. We need to continuously refactor both source and test codes while we build the component. Let's modify the input in the previous test case to make the tests pass.

var input = [{
name: 'Title 1',
content: 'Content belongs to title 1',
showOnLoad: true
},{
name: 'Title 2',
content: 'Content belongs to title 2',
showOnLoad: true
}];

This is the beauty of TDD; designing the component step by step. By now, we made our component configurable also.

Test Case 4:

It should be able to toggle the content by clicking on the respective title.

it('should be able to toggle the content by clicking on the respective title.', function(){
var input = [{
name: 'Title 1',
content: 'Content belongs to title 1'
},{
name: 'Title 2',
content: 'Content belongs to title 2'
}];

var accordion = TestUtils.renderIntoDocument( <Accordion data={input}/> );
var headers = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-header');
var contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');

expect(contents.length).toEqual(0);
TestUtils.Simulate.click(headers[0]);
contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');
expect(contents.length).toEqual(1);
expect(contents[0].textContent).toEqual('Content belongs to title 1');
TestUtils.Simulate.click(headers[0]);
contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');
expect(contents.length).toEqual(0);
});

The tests are RED again. Before we move on, it's time to think about the code design again. If you obeserve, we have a stateful component now. It means, each of the pane in the Accordion can have its own closed or open states.

While designing your applications, it's a bad practice to put whole logic into one single component. We should think about small components -- which handles single tasks -- and create composite components for big features. Here, in our code we should move the state-full code into a separate component; Let's call it as a Pane component.

See the code below:

'use strict';

var React = require('react');

var Pane = React.createClass({
getInitialState: function(){
return {
show: this.props.data.showOnLoad
};
},

toggle: function(){
this.setState({
show: !this.state.show
});
},

render: function(){
var getContent = (function(item){
return this.state.show ? (
<div className="accordion-content">
{item.content}
</div>
) : '';
}).bind(this);

var item = this.props.data;

return (
<div>
<div className="accordion-header" onClick={this.toggle}>
{item.name}
</div>
{ getContent(item) }
</div>
);
}
});

var Accordion = React.createClass({
render: function(){
var panes = [];
var data = this.props.data || [];

data.forEach(function(item, index){
panes.push(
<Pane data={item} key={index}/>
);
});

return (
<div className="accordion">
{panes}
</div>
);
}
});

module.exports = Accordion;

All tests are GREEN now ! If you check your browser window ( where the server is running ), you can see that our Accordion component is functional.

Before we summarise, see the final source code and tests:

jest.dontMock('../scripts/accordionComponent.js');

describe('Accordion', function() {
var React = require('react');
var TestUtils = require('react-addons-test-utils');
var Accordion;

beforeEach(function() {
Accordion = require('../scripts/accordionComponent');
});

it('should exists', function() {
// Render into document
var accordion = TestUtils.renderIntoDocument( <Accordion /> );
expect(TestUtils.isCompositeComponent(accordion)).toBeTruthy();
});

it('should build the layout from an array of objects passed as prop', function() {

var input = [{
name: 'Title 1',
content: 'Content belongs to title 1',
showOnLoad: true
},{
name: 'Title 2',
content: 'Content belongs to title 2',
showOnLoad: true
}];

var accordion = TestUtils.renderIntoDocument( <Accordion data={input}/> );
var headers = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-header');
var contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');

expect(headers.length).toEqual(2);
expect(contents.length).toEqual(2);

expect(headers[0].textContent).toEqual('Title 1');
expect(headers[1].textContent).toEqual('Title 2');

expect(contents[0].textContent).toEqual('Content belongs to title 1');
expect(contents[1].textContent).toEqual('Content belongs to title 2');
});

it('should hide all the contents by default unless specified by a flag', function(){
var input = [{
name: 'Title 1',
content: 'Content belongs to title 1'
},{
name: 'Title 2',
content: 'Content belongs to title 2',
showOnLoad: true
}];

var accordion = TestUtils.renderIntoDocument( <Accordion data={input}/> );
var contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');
expect(contents.length).toEqual(1);
expect(contents[0].textContent).toEqual('Content belongs to title 2');
});

it('should be able to toggle the content by clicking on the respective title.', function(){
var input = [{
name: 'Title 1',
content: 'Content belongs to title 1'
},{
name: 'Title 2',
content: 'Content belongs to title 2'
}];

var accordion = TestUtils.renderIntoDocument( <Accordion data={input}/> );
var headers = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-header');
var contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');

expect(contents.length).toEqual(0);
TestUtils.Simulate.click(headers[0]);
contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');
expect(contents.length).toEqual(1);
expect(contents[0].textContent).toEqual('Content belongs to title 1');
TestUtils.Simulate.click(headers[0]);
contents = TestUtils.scryRenderedDOMComponentsWithClass(accordion, 'accordion-content');
expect(contents.length).toEqual(0);
});

});
'use strict';

var React = require('react');

var Pane = React.createClass({
getInitialState: function(){
return {
show: this.props.data.showOnLoad
};
},

toggle: function(){
this.setState({
show: !this.state.show
});
},

render: function(){
var getContent = (function(item){
return this.state.show ? (
<div className="accordion-content">
{item.content}
</div>
) : '';
}).bind(this);

var item = this.props.data;

return (
<div>
<div className="accordion-header" onClick={this.toggle}>
{item.name}
</div>
{ getContent(item) }
</div>
);
}
});

var Accordion = React.createClass({
render: function(){
var panes = [];
var data = this.props.data || [];

data.forEach(function(item, index){
panes.push(
<Pane data={item} key={index}/>
);
});

return (
<div className="accordion">
{panes}
</div>
);
}
});

module.exports = Accordion;
'use strict';

var React = require('react');
var ReactDOM = require('react-dom');
var Accordion = require('components/accordionComponent');
var input = [{
name: 'Title 1',
content: 'Content belongs to title 1'
},{
name: 'Title 2',
content: 'Content belongs to title 2'
}];

ReactDOM.render(<Accordion data={input}/>, document.getElementById('view'));

Summary

When I saw ReactJs first time, I didn't like the syntax at all. I watched the project grow with quite skepticism. Later, I got chance to work with it, and then I knew how powerful it was. Writing code in React really changed my thinking process about a UI driven application. Now I started thinking everything in terms of components, and I know that's the future of web development.

This article is my attempt to mix TDD with ReactJs . Here, we saw how to make a React component from scratch using TDD approach. I hope this tutorial is useful for everyone. Feedbacks are most welcome.

Comments

← Home