Report this

What is the reason for this report?

An Overview of Mock Functions With Jest

Published on June 1, 2017
Matthew Garcia

By Matthew Garcia

An Overview of Mock Functions With Jest

A higher order function takes a function and returns a function. Jest offers a way to make sure the function you gave is being used right.

Testing a Higher Order Function

Let’s say you want to write a memoization function. It might look something like:

// memoize.js
export default function memoize(func) {
  return function (key) {
    const registry = new Map();
    let value = registry.get(key);
    if (typeof value === 'undefined') {
      value = func(key);
      registry.set(key, value);
    }
    return value;
  }
}

And to test it, you’d have something like:

import memoize from './memoize';

it('memoizes `func`.', () => {
  // `func` here just cubes the input.
  const func = value => Math.pow(value, 3);
  const memoizedFunc = memoize(func);
  expect(memoizedFunc(3)).toEqual(27);
  expect(memoizedFunc(4)).toEqual(64);
  expect(memoizedFunc(3)).toEqual(27);
  expect(memoizedFunc(5)).toEqual(125);
});

yarn run test, everything passes, we’re done, right?

The Trouble With Testing Higher Order Functions

Except there’s a problem with memoize. Did you catch it? The issue is that you’re testing the resultant function, but not how the input function is being used. To do this, Jest provides mock functions.

Creating a Mock Function

It’s pretty simple; just pass an implementation function to jest.fn and it’ll give you a mock function.

Hey, that’s a higher order function, too!

Let’s use this to test memoize a bit better:

import memoize from './memoize';

it('memoizes `func`.', () => {
  // A mock function: a function wrapped in `jest.fn`.
  const func = jest.fn(value => Math.pow(value, 3));
  const memoizedFunc = memoize(func);
  expect(memoizedFunc(3)).toEqual(27);
  expect(memoizedFunc(4)).toEqual(64);
  expect(memoizedFunc(3)).toEqual(27);
  expect(memoizedFunc(5)).toEqual(125);
  // Mock functions have a few special matchers available to them.  Let's take a look.
  // `func` was called.
  expect(func).toHaveBeenCalled();
  // `func` has been called with 5.
  expect(func).toHaveBeenCalledWith(4);
  // `func` was last called with 5.
  expect(func).toHaveBeenLastCalledWith(5);
  // `func` was called thrice (since the second 3 was supposed to be memoized).
  // Supposed to.
  expect(func).toHaveBeenCalledTimes(3);
});

Now that you’re testing how the function is used, you can catch that error in memoize.

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

Learn more about our products

About the author

Matthew Garcia
Matthew Garcia
Author
Category:
Tags:
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.

Still looking for an answer?

Was this helpful?


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!

Creative CommonsThis work is licensed under a Creative Commons Attribution-NonCommercial- ShareAlike 4.0 International License.
Join the Tech Talk
Success! Thank you! Please check your email for further details.

Please complete your information!

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.