jest-mock vs sinon vs testdouble
JavaScript Mocking Libraries Comparison
3 Years
jest-mocksinontestdoubleSimilar Packages:
What's JavaScript Mocking Libraries?

Mocking libraries in JavaScript are tools that allow developers to create mock objects, functions, or modules in their tests. These mocks simulate the behavior of real objects in a controlled way, enabling developers to isolate and test specific parts of their code without relying on external dependencies. Mocking is particularly useful for testing functions that interact with APIs, databases, or other external systems, as it allows for predictable and repeatable tests. Popular mocking libraries include jest-mock, sinon, and testdouble, each offering unique features and capabilities for creating mocks, stubs, and spies in JavaScript applications.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
jest-mock42,518,503
45,02555.4 kB2532 months agoMIT
sinon8,264,282
9,7392.08 MB463 months agoBSD-3-Clause
testdouble170,096
1,428465 kB34a year agoMIT
Feature Comparison: jest-mock vs sinon vs testdouble

Integration with Testing Frameworks

  • jest-mock:

    jest-mock is tightly integrated with the Jest testing framework, making it the best choice for projects that already use Jest. It leverages Jest's features, such as snapshot testing and parallel test execution, to provide a seamless mocking experience.

  • sinon:

    sinon is framework-agnostic and can be used with any testing framework, including Mocha, Jasmine, and Jest. This makes it a versatile choice for projects that may not be tied to a specific testing tool.

  • testdouble:

    testdouble is also framework-agnostic, but it is designed to work well with modern JavaScript and encourages a clean, declarative style of testing. It can be easily integrated into any testing setup.

API Design

  • jest-mock:

    jest-mock provides a simple and intuitive API for creating mocks and spies. Its design is focused on ease of use, with clear documentation and examples that make it easy for developers to get started quickly.

  • sinon:

    sinon offers a more comprehensive API that provides detailed control over mocking, stubbing, and spying. While it may have a steeper learning curve, its flexibility and power make it worth the investment for complex testing scenarios.

  • testdouble:

    testdouble features a clean and minimalist API that reduces boilerplate code and emphasizes readability. It encourages developers to write clear and concise tests, making it a great choice for teams that value simplicity.

Mocking Capabilities

  • jest-mock:

    jest-mock excels at mocking functions and modules, with built-in support for mocking timers and handling asynchronous code. It provides automatic mocking features that can simplify the process of creating mocks, especially for large codebases.

  • sinon:

    sinon is known for its powerful and flexible mocking capabilities, including support for deep mocking, partial mocking, and creating fake timers. It allows for fine-grained control over how functions behave during tests, making it ideal for complex scenarios.

  • testdouble:

    testdouble focuses on creating high-quality mocks and stubs with minimal effort. It encourages best practices in mocking and provides tools to create realistic doubles without the need for extensive configuration.

Community and Ecosystem

  • jest-mock:

    jest-mock benefits from the large and active Jest community, which contributes to its ongoing development and provides a wealth of resources, plugins, and integrations. This makes it a reliable choice for projects that want to stay up-to-date with the latest testing trends.

  • sinon:

    sinon has a long-established community and a rich ecosystem of plugins and extensions. Its maturity and stability make it a trusted choice for projects that require robust mocking capabilities.

  • testdouble:

    testdouble is a newer library with a growing community that values simplicity and good design. While it may not have as many plugins as Jest or Sinon, its focus on quality and usability makes it a promising choice for modern projects.

Code Example

  • jest-mock:

    Mocking a function with jest-mock

    const myFunction = jest.fn();
    myFunction.mockReturnValue(42);
    console.log(myFunction()); // 42
    
  • sinon:

    Mocking a function with sinon

    const sinon = require('sinon');
    const myFunction = sinon.stub();
    myFunction.returns(42);
    console.log(myFunction()); // 42
    
  • testdouble:

    Mocking a function with testdouble

    import td from 'testdouble';
    const myFunction = td.function();
    td.when(myFunction()).thenReturn(42);
    console.log(myFunction()); // 42
    
How to Choose: jest-mock vs sinon vs testdouble
  • jest-mock:

    Choose jest-mock if you are already using Jest as your testing framework and need a simple, integrated solution for mocking functions, modules, and timers. It offers a straightforward API and is optimized for use with Jest's testing environment.

  • sinon:

    Choose sinon if you need a standalone library that provides powerful and flexible mocking, stubbing, and spying capabilities. It works well with any testing framework and is ideal for projects that require fine-grained control over how functions behave during tests.

  • testdouble:

    Choose testdouble if you want a modern, minimalist approach to mocking that emphasizes simplicity and readability. It encourages good testing practices and provides a clean API for creating doubles (mocks, stubs, and spies) without a lot of boilerplate code.

README for jest-mock

jest-mock

Note: More details on user side API can be found in Jest documentation.

API

import {ModuleMocker} from 'jest-mock';

constructor(global)

Creates a new module mocker that generates mocks as if they were created in an environment with the given global object.

generateFromMetadata(metadata)

Generates a mock based on the given metadata (Metadata for the mock in the schema returned by the getMetadata() method of this module). Mocks treat functions specially, and all mock functions have additional members, described in the documentation for fn() in this module.

One important note: function prototypes are handled specially by this mocking framework. For functions with prototypes, when called as a constructor, the mock will install mocked function members on the instance. This allows different instances of the same constructor to have different values for its mocks member and its return values.

getMetadata(component)

Inspects the argument and returns its schema in the following recursive format:

{
  type: ...
  members: {}
}

Where type is one of array, object, function, or ref, and members is an optional dictionary where the keys are member names and the values are metadata objects. Function prototypes are defined by defining metadata for the member.prototype of the function. The type of a function prototype should always be object. For instance, a class might be defined like this:

const classDef = {
  type: 'function',
  members: {
    staticMethod: {type: 'function'},
    prototype: {
      type: 'object',
      members: {
        instanceMethod: {type: 'function'},
      },
    },
  },
};

Metadata may also contain references to other objects defined within the same metadata object. The metadata for the referent must be marked with refID key and an arbitrary value. The referrer must be marked with a ref key that has the same value as object with refID that it refers to. For instance, this metadata blob:

const refID = {
  type: 'object',
  refID: 1,
  members: {
    self: {ref: 1},
  },
};

Defines an object with a slot named self that refers back to the object.

fn(implementation?)

Generates a stand-alone function with members that help drive unit tests or confirm expectations. Specifically, functions returned by this method have the following members:

.mock

An object with three members, calls, instances and invocationCallOrder, which are all lists. The items in the calls list are the arguments with which the function was called. The "instances" list stores the value of 'this' for each call to the function. This is useful for retrieving instances from a constructor. The invocationCallOrder lists the order in which the mock was called in relation to all mock calls, starting at 1.

.mockReturnValueOnce(value)

Pushes the given value onto a FIFO queue of return values for the function.

.mockReturnValue(value)

Sets the default return value for the function.

.mockImplementationOnce(function)

Pushes the given mock implementation onto a FIFO queue of mock implementations for the function.

.mockImplementation(function)

Sets the default mock implementation for the function.

.mockReturnThis()

Syntactic sugar for:

mockFn.mockImplementation(function () {
  return this;
});

In case both .mockImplementationOnce() / .mockImplementation() and .mockReturnValueOnce() / .mockReturnValue() are called. The priority of which to use is based on what is the last call:

  • if the last call is .mockReturnValueOnce() or .mockReturnValue(), use the specific return value or default return value. If specific return values are used up or no default return value is set, fall back to try .mockImplementation();
  • if the last call is .mockImplementationOnce() or .mockImplementation(), run the specific implementation and return the result or run default implementation and return the result.
.withImplementation(function, callback)

Temporarily overrides the default mock implementation within the callback, then restores it's previous implementation.

If the callback is async or returns a thenable, withImplementation will return a promise. Awaiting the promise will await the callback and reset the implementation.