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-query-test

v0.2.11

Published

An expressive testing library for React

Downloads

42

Readme

react-query-test npm install react-query-test

An expressive testing library for React:

import React, { useState } from "react";
import $ from "react-query-test";

const Counter = () => {
  const [counter, setCounter] = useState(0);
  const increment = () => setCounter(counter + 1);
  return <div onClick={increment}>{counter}</div>;
};

it("Increments the counter one at a time", async () => {
  const $counter = $(<Counter />);
  expect($counter.text()).toEqual("0");
  await $counter.click();
  expect($counter.text()).toEqual("1");
  await $counter.click();
  expect($counter.text()).toEqual("2");
});

The interface is a subset of jQuery, where you can navigate the DOM once it has been created:

const Counter = () => {
  const [counter, setCounter] = useState(0);
  const increment = () => setCounter(counter + 1);
  return <div><button onClick={increment}>{counter}</button></div>;
};

it('Also works with nested events', async () => {
  const $dom = $(<Counter />);
  expect($dom.text()).toEqual("0");
  await $dom.click();
  expect($dom.text()).toEqual("0");
  await $dom.click('button');
  // Same as: await $dom.find('button').click();
  expect($dom.text()).toEqual("1");
});

For .click(), you can pass a selector and/or a running time:

  • .click('button') (string): the child element that receives the click. Leave it empty to click the current element. This is a shorthand of .find(selector).click() for convenience.
  • .click(100) (number): the time to wait after the click for the effect to be settled. If they are not immediate (API call, timeouts, transitions, etc) make sure that the time is longer than the effect. Internally this will wrap the effect with an act() that works for the specified time.

You can combine them as well:

it('clicks all buttons inside and wait 200ms', async () => {
  const $dom = $(<Counter />);
  expect($dom.text()).toEqual("0");
  await $dom.click('button', 200);
  expect($dom.text()).toEqual("1");
});

API

Unknown: .size(), .value(), .checked

$() ✅

.attr() ✅

.children() ❌

.click() ✅

.closest() ❌

.data() ❌

.each() ❌

.filter() ❌

.find() ✅

.first() ✅

.html() ✅

.is() ❌

.last() ✅

.map() ✅

.parent() ❌

.siblings() ❌

.text() ✅

.trigger() ✅