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

jest-mock-react-noop

v2.0.1

Published

Mock React components to noops with Jest.

Downloads

8

Readme

jest-mock-react-noop

Mock React components to noops with Jest.

⚛️:construction::goat:

Remember shallow rendering from enzyme? Wish you could have it with @testing-library/react? Now you can!

Use jest.mock to re-define react as jest-mock-react-noop, providing it with an argument indicating the component(s) under test. jest-mock-react-noop returns a monkeypatched version of React with a modified createElement function. When rendering, any component not under test will be replaced with one that returns a placeholder empty div with a data-jest-mock-react-noop attribute whose value is that component's name.

You can query for placeholder divs using the following query functions (similar to @testing-library's query functions):

  • getByNoop
  • getAllByNoop
  • queryByNoop
  • queryAllByNoop
import "@testing-library/jest-dom";
import * as React from "react";
import { renderWithNoop } from "jest-mock-react-noop";
import { App } from "../App";

jest.mock("react", () =>
  // @ts-ignore
  require("jest-mock-react-noop").default('App')
);

describe("App", () => {
  test("works", () => {
    const { queryByNoop } = renderWithNoop(<App />);

    // Assert that a nested component is rendered only as a noop.
    expect(queryByNoop('Other')).toBeInTheDocument();
  });
});

You can match components by name with string:

require("jest-mock-react-noop").default('App')

Or with regular expression:

require("jest-mock-react-noop").default(/App/)

Or with a function returning a boolean (which also gives you access to the component constructor):

require("jest-mock-react-noop").default(
  // `name` is the component name/string
  // `type` is the function/constructor or tag name string
  (name, type) => return ['App', 'MyComponent'].includes(name)
)

If you prefer to configure queries manually and use the native render instead of our renderWithNoop, you can import either noopQueries (with type NoopQueries) or noopQueriesWithDefaults (with type and NoopQueriesWithDefaults, which includes the defaults from @testing-library/react).

import { render, queries } from "@testing-library/react";
import { noopQueries, NoopQueriesWithDefaults} from "..";

describe("App", () => {
  test("works", () => {
    const { queryByNoop, queryByTestId } = render<NoopQueriesWithDefaults>(<App />, {
      queries: {
        ...queries,
        ...noopQueries
      }
    });
  });
});
import { render } from "@testing-library/react";
import { noopQueriesWithDefaults, NoopQueriesWithDefaults} from "..";

describe("App", () => {
  test("works", () => {
    const { queryByNoop, queryByTestId } = render<NoopQueriesWithDefaults>(<App />, {
      queries: noopQueriesWithDefaults
    });
  });
});

Sometimes jest.mock as above won't work, e.g., with ts-jest you might get this error:

TypeError: require(...).default is not a function

If so, you can try this:

jest.mock("react", () => ({
  ...jest.requireActual('react'),
  createElement: jest.fn()
}));

React.createElement.mockImplementation(
  // @ts-ignore
  require('jest-mock-react-noop').default('App').createElement
);