Click here to Skip to main content
15,885,896 members
Articles / DevOps / Testing

Testing for PropType Errors in React

Rate me:
Please Sign up or sign in to vote.
5.00/5 (1 vote)
1 Nov 2016CPOL1 min read 4.2K  
How to test for PropType Errors in React

Testing PropType Errors

You might have a nice set of React tests, but are you checking for PropTypes errors? Wouldn’t it be nice to get failing tests whenever you forget to pass a required prop? Well, today is your lucky day.

You can test that no errors are printed to the console – this verifies that you didn’t forget any required props, among other things. You can use the Sinon library to do this, or your favorite spying library:

Check For Errors In One Test

JavaScript
// first:  npm install --save-dev sinon
import sinon from 'sinon';

// At the top of your tests:
beforeEach(() => {
  sinon.stub(console, 'error');
});

afterEach(() => {
  console.error.restore();
});

it('ensures no errors', () => {
  // ... do the test setup here ...

  // Make sure no errors were printed
  sinon.assert.notCalled(console.error);
});

DRY It Up

However, this code can get repetitive real fast. If you want to DRY it out, extract the code into a module like this:

JavaScript
// test-utils.js

import sinon from 'sinon';

export function stubConsoleError() {
  beforeEach(() => {
    sinon.stub(console, 'error');
  });

  afterEach(() => {
    console.error.restore();
  });
}

And then in your tests, import and call that function:

JavaScript
import { stubConsoleError } from './test-utils';

stubConsoleError();

it('ensures no errors', () => {
  // ... do the test setup here ...

  // Make sure no errors were printed
  sinon.assert.notCalled(console.error);
});

Never Allow Errors

And hey, maybe you want to go one step further and ensure that none of your tests print errors. You could move that assertion into the afterEach block like so:

JavaScript
// test-utils.js

import sinon from 'sinon';

export function noErrorsAllowed() {
  beforeEach(() => {
    sinon.stub(console, 'error');
  });

  afterEach(() => {
    sinon.assert.notCalled(console.error);
    console.error.restore();
  });
}

Then import it, call it, and you’re all set.

JavaScript
import { noErrorsAllowed } from './test-utils';

noErrorsAllowed();

it('works great', () => {
  // just write your test
  // the afterEach will check for errors
});

Check For Specific Errors

If you’d like to be a little more choosy about which errors you expect, you can check that console.error was called with specific text with a function like this:

JavaScript
function expectMissingProp(prop, component) {
  sinon.assert.calledWithMatch(console.error,
    new RegExp(`Required prop \`${prop}\` was not specified in \`${component}\``));
}

it('warns about missing props', () => {
  ReactDOM.render(<Person/>, div);

  // Require exactly 2 errors with specific text
  sinon.assert.callCount(console.error, 2);
  expectMissingProp('firstName', 'Person');
  expectMissingProp('lastName', 'Person');
});

Finito

There you go: now you can directly test for missing props in your unit tests.

Testing for PropType Errors in React was originally published by Dave Ceddia at Angularity on October 31, 2016.

This article was originally posted at https://daveceddia.com/feed.xml

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
United States United States
Dave is a Software Engineer in the Boston area and writes about AngularJS and other JavaScript things over at daveceddia.com

Comments and Discussions

 
-- There are no messages in this forum --