Tutorial

Testing React / Redux Apps with Jest & Enzyme - Part 4: Testing Redux Reducers

Published on July 10, 2018
Default avatar

By Jasper Valero

Testing React / Redux Apps with Jest & Enzyme - Part 4: Testing Redux Reducers

While we believe that this content benefits our community, we have not yet thoroughly reviewed it. If you have any suggestions for improvements, please let us know by clicking the “report an issue“ button at the bottom of the tutorial.

This is part 4 of a 4-part series on testing React / Redux apps using both Jest and Enzyme for a robust testing solution. In this part we’ll cover some simple examples on how to test Redux reducers.

The series

Continuing with testing Redux, we’ll finish out this series by showing you how to test your reducers. Reducers are what complete the render chain in React / Redux applications. They update our state when an action is taken, which causes React to re-render the UI.

Let’s do it!

Setup the Test Suite

The first thing to do is to import the reducer we want to test and our action types. We’ll also go ahead and write the describe() block to encapsulate our test suite for this reducer.

The action types file exports constants that map to the string value of each action.

__tests__/reducers/select_reducer.test.js
// Reducer to be tested
import selectReducer from '../../reducers/select_reducer';
import {
  SELECT_AVATAR, // Only ones related to the reducer being tested
} from '../../actions/types';

describe('select_reducer', () => {
  // ...
});

Take a moment to look at the code above. You may notice a few omissions from the setup code we used for testing actions. We didn’t mock out our store. That means we don’t need to import the redux-mock-store package. We also don’t need to run clearActions() before each test. This is because we’ll test the result returned from our reducers after calling them directly. We won’t dispatch() them into our store like we did with the actions.

Test Your Reducers

Let’s first test our initial state. We do this by passing a dummy action into our reducer. I have a switch statement in the reducer with a default case. If the action type is unrecognized by the reducer then it returns the current, unmodified state. Otherwise, it returns the modified state. So by passing in a dummy action we can test our initialState (since we run this test first).

__tests__/reducers/select_reducer.test.js

// ...

describe('INITIAL_STATE', () => {
  test('is correct', () => {
    const action = { type: 'dummy_action' };
    const initialState = { selectedAvatar: 0 };

    expect(selectReducer(undefined, action)).toEqual(initialState);
  });
});

// ...

Next let’s test that our reducer modifies our state as expected when passed a recognized action and payload.

__tests__/reducers/select_reducer.test.js

// ...

describe('SELECT_AVATAR', () => {
  test('returns the correct state', () => {
    const action = { type: SELECT_AVATAR, payload: 1 };
    const expectedState = { selectedAvatar: 1 };

    expect(selectReducer(undefined, action)).toEqual(expectedState);
  });
});

// ...

Snapshots

Just like with actions and components, once you have your tests passing you can leverage Snapshots and cut out a few lines of code:

__tests__/reducers/select_reducer.test.js

// ...

describe('INITIAL_STATE', () => {
  test('is correct', () => {
    const action = { type: 'dummy_action' };

    expect(selectReducer(undefined, action)).toMatchSnapshot();
  });
});

describe('SELECT_AVATAR', () => {
  test('returns the correct state', () => {
    const action = { type: SELECT_AVATAR, payload: 1 };

    expect(selectReducer(undefined, action)).toMatchSnapshot();
  });
});

// ...

Bonus Tip!

Group your reducers into similar functionality whenever possible. With our selectReducers file we worked with the SELECT_AVATAR action type, yet there could easily be additional ones like SELECT_USER, SELECT_THEME, and so on in the same reducer. By grouping them together we improve our application architecture. If their functionality is similar we can apply the DRY principle. We have more opportunities to reuse code and write test helpers that can cover all like reducers.

Conclusion

In Part 1 of this series I showed you how to install and setup Jest and Enzyme. In Part 2 I covered testing React components. In Part 3 I covered testing Redux actions. And we finished up in this post with testing reducers.

You should now have a well rounded setup and accompanying knowledge to test your React / Redux applications. Testing doesn’t have to be difficult. Thank you for following along!

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about us


About the authors
Default avatar
Jasper Valero

author

Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?
 
Leave a comment


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Join the Tech Talk
Success! Thank you! Please check your email for further details.

Please complete your information!

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel