npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-jest-mock

v0.0.13

Published

Mock react components with a simple method.

Downloads

147

Readme

React Jest Mock

Mock React components with just one line. Isolate your unit tests while controlling how nested components behave.

Getting started

  1. Create a component mock through jest __mocks__ folder.
import { mockComponent } from 'react-jest-mock';

const MyDependency = mockComponent({name: "MyDependency"});

export default MyDependency;
  1. Mock your dependencies in your unit test.
import { render } from '@testing-library/react';

import MyDependency from './my-dependency';
import MyOtherDependency from './my-other-dependency';

import MyComponent from './my-component';

// Manually invoke jest.mock if needed.
jest.mock('./my-dependency');

// The mock can also be created inline through jest.requireActual
jest.mock('/my-other-dependency', () => {
    const mockComponent = jest.requireActual("react-jest-mock").mockComponent;
    return mockComponent({ name: "MyOtherDependency" });
})

describe('...', () => {
    it('...', () => {
        render(<MyComponent />);

        expect(MyDependency).toHaveBeenRendered();
    })

    it('...', () => {
        render(<MyComponent />);

        expect(MyOtherDependency).toHaveBeenRendered();
    })
});

Configuration

By default mockComponent() will just render a div element. This behavior and more can be change by passing an optional parameter to the function.

const settings = {
    name: 'MyDependency', // Component name. Used for error messages.
    as: 'input', // Controls what element will be render on the dom. Supported values are: input, button, label and div.
    ref: {}, // Reference exposed by the component.
    renderProps: ['propName'], // Array of prop names which should also be rendered.
}
const MyDependency = mockComponent(settings);

Custom matchers

  1. toHaveBeenRendered
import { render } from '@testing-library/react';

import MyDependency from './my-dependency';

import MyComponent from './my-component';

// Manually invoke jest.mock if needed.
jest.mock('./my-dependency');

describe('...', () => {
    it('...', () => {
        render(<MyComponent />);

        expect(MyDependency).toHaveBeenRendered();
    })
});
  1. toHaveBeenRenderedTimes
import { render } from '@testing-library/react';

import MyDependency from './my-dependency';

import MyComponent from './my-component';

// Manually invoke jest.mock if needed.
jest.mock('./my-dependency');

describe('...', () => {
    it('...', () => {
        render(<MyComponent />);

        expect(MyDependency).toHaveBeenRenderedTimes(1);
    })
});
  1. toHaveBeenRenderedWith
import { render } from '@testing-library/react';

import MyDependency from './my-dependency';

import MyComponent from './my-component';

// Manually invoke jest.mock if needed.
jest.mock('./my-dependency');

describe('...', () => {
    it('...', () => {
        render(<MyComponent />);

        expect(MyDependency).toHaveBeenRenderedWith({name: 'test'});
    })
});
  1. toHaveBeenNthRenderedWith
import { render } from '@testing-library/react';

import MyDependency from './my-dependency';

import MyComponent from './my-component';

// Manually invoke jest.mock if needed.
jest.mock('./my-dependency');

describe('...', () => {
    it('...', () => {
        render(<MyComponent />);

        expect(MyDependency).toHaveBeenNthRenderedWith(1, {name: 'test'});
    })
});

Firing events

Components callbacks can be invoke through "fireCallback" utility function. Note that this utility is prepared to handle async callbacks too so it should be awaited.

await fireCallback(MyDependency, "myCb", argsArray, nthCalled);