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

react-testing-kit

v2.1.0

Published

[![Actions Status](https://github.com/mAAdhaTTah/react-testing-kit/workflows/Run%20tests/badge.svg)](https://github.com/mAAdhaTTah/react-testing-kit/actions)

Readme

react-testing-kit

Actions Status

A testing library to enable reusable, readable logic in your unit tests.

How to Use

Install react-testing-kit:

npm i -D react-testing-kit
# or with yarn
yarn --dev react-testing-kit

Import it into your tests:

import { Kit } from 'react-testing-kit';
import { render, fireEvent, waitFor, waitForElementToBeRemoved } '@testing-library/react';

Create your test kit.

const kit = Kit.create(render, MyComponent, () => ({
  // Default props
}))
  .setElements(queries => ({
    button: () => queries.getByTestId('button'),
  }))
  .setFire(elements => ({
    buttonClick: () => fireEvent.click(elements.button()),
  }))
  .setAsync(elements => ({
    buttonToBeRemoved: () => waitForElementToBeRemoved(elements.button),
  }));

Create an instance of the kit. You can override any default props by passing in those values.

const run = kit.run({
  // ... overridden props
});

Test the component instance.

const button = run.elements.button();
run.fire.buttonClick();
await run.waitFor.button();
await run.waitFor.buttonToBeRemoved();
expect(run.queries.container).toMatchSnapshot();

How It Works

The created kit ties together the component to a reusable set of a functions that can be shared across test runs. This instance is typesafe, enabling a structure for interacting with a rendered components.

elements is called with the return of render, enabling the creation of functions to fetch particular elements in the component. These elements are then passed to fire & waitFor, allowing those elements to be bound to particular interactions.

This encourages a test API that's consistent, making complex tests more readable by providing named functions instead of a complex binding between RTL's queries & fireEvent. It also limits the ability to write custom queries & events in your tests, ensuring simple, readable logic in your tests.

API

Kit

Base class that provides the structure for a test kit. The basic API is as follows:

Kit#create

Static method to create a new test kit. Accepts a custom render function, the component under test, and a function to generate default props for the component.

let kit = Kit.create(render, TestComponent, () => ({}));

kit.setElements

Set the function that will create the elements property on the RunInstance. It will receive the return value of the render function and should return an object with methods to query interesting elements in your component. It will return a new kit instance, allowing you to fluently build up your testing kit in a typesafe way.

kit = kit.setElements(queries => ({
  button: () => queries.getByLabelText('Click me'),
}));

kit.setFire

Set the function that will create the fire property on the RunInstance. It will receive the return value of the setElements function and should return an object with methods to fire interesting events on the elements in your component. It will return a new kit instance, allowing you to fluently build up your testing kit in a typesafe way.

kit = kit.setFire(elements => ({
  buttonClick: () => fireEvent.click(elements.button()),
}));

kit.setAsync

Set the function that will create the waitFor property on the RunInstance. It will receive the return value of the setElements function and should return an object with methods to fire interesting events on the elements in your component. It will return a new kit instance, allowing you to fluently build up your testing kit in a typesafe way.

kit = kit.setAsync(elements => ({
  buttonToBeRemoved: () => waitForElementToBeRemoved(elements.button),
}));

kit.run

Run the test kit and create a new RunInstance. Accepts an object of props to override from the default props. This RunInstance will have the following properties:

  • props - The result of combining the component props & its overrides.
  • queries - The result of the provided render function.
  • elements - The result of the function provided to setElements.
  • fire - The result of the function provided to setFire.
  • waitFor - The result of the function provided to setAsync.
const run = kit.run({
  // ... override props
});