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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ryanbrandt/react-testing-utils

v0.5.0

Published

Jest/React/RTL component unit testing utilities

Readme

react-testing-utils

Wrappers and utilities for unit testing React components with Jest and React Testing Library.

Usage

yarn add @ryanbrandt/react-testing-utils

// or

npm install @ryanbrandt/react-testing-utils

Required Peer Dependencies

"peerDependencies": {
  "@testing-library/dom": ">=8.13.0",
  "@testing-library/jest-dom": ">=5.14.1",
  "@testing-library/react": ">=12.1.2",
  "@testing-library/user-event": ">=14.1.0",
  "jest": ">=28.1.0",
  "jest-environment-jsdom": ">=28.1.0",
  "react": ">=17.0.2",
  "react-dom": ">=17.0.2",
}

API

Mocking Function Components

jest.mock("path/to/component");
const mockFunctionComponent = new MockFunctionComponent(MyFunctionComponent);

Mocking Class Components

jest.mock("path/to/component");
const mockClassComponent = new MockClassComponent(MyClassComponent);

Methods

Setup

A setup is provided by default as <div data-testid={MockComponent.DATA_TEST_ID} /> when instantiated.

However, if a specific setup is needed, you can define your own. Each mock provided mock setup will be wrapped in a div as follows: <div data-testid={MockComponent.DATA_TEST_ID}>{MockSetup}</div>

// Function

mockFunctionComponent.mockReturnValue(<div />);
mockFunctionComponent.mockImplementation((props) => <div>{children}</div>);

// Class

mockClassComponent.mockRenderReturnValue(<div />);
mockClassComponent.mockRenderImplementation((props) => (
  <div>{props.children}</div>
));

Getters

it("renders one instance", () => {
  ...
  expect(mockComponent.mockRoot).toBeInTheDocument();
});

it("renders many instances", () => {
  expect(mockComponent.mockRoots.length).toBeGreaterThan(1);
});

Click Interactions


it("does something when clicked", async () => {
  ...
  await mockComponent.click();
});

it("does something when an instance is clicked", async () => {
  ...
  await mockComponent.clickInstance(1);
});

Typing Interactions


it("does something when typed into", async () => {
  ...
  await mockComponent.type("Foo");
});

it("does something when an instance is typed into", async () => {
  ...
  await mockComponent.typeInstance("Foo", 1);
});

Screen Assertions

it("is on the screen", () => {
  ...
  mockComponent.assertOnScreen();
});

it("is not on the screen", () => {
  ...
  mockComponent.assertNotOnScreen();
});

Invocation Assertions

it("is called with what I expect", () => {
  ...
  mockComponent.assertCalledWith({
    foo: "bar",
  });
});

it("is called with what I expect when I expect it", () => {
  ...
  mockComponent.assertNthCalledWith({
    foo: "bar",
  }, 1);
});

it("is last called with what I expect", () => {
  ...
  mockComponent.assertLastCalledWith({
    foo: "bar"
  });
});