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

try-hard

v1.0.2

Published

Simple tool to use in your tests when you don't control the timing

Downloads

208

Readme

Try Hard

tryHard is a convenient tool when writing your Javascript tests and you need to test asynchronous state changes with no control on the timing.
It is particularly useful for integration tests.

API

tryHard takes as a first argument a function that can fail (ie. that throws) or that can pass (ie. that doesn't throw)

It calls the function many times (by default every 25ms) until:

  • it finally passes
  • or it reached the timeout (by default 2 seconds), in which case it fails and rethrow the error of the inner function

tryHard returns a promise. You can use the .then() and .catch() to end your test.
The easiest way is to use ES7 async/await and simply await tryHard() in your test

async function tryHard(testable: Function, options?: TryHardOptions)

type TryHardOptions = {
  interval?: number, // time in milliseconds between each try
  timeout?: number, // time in milliseconds to wait before failing
}

Examples

Typical example when writing an integration test:

it('updates the application state', async () => {
  assert(myApplicationState.dataIsFetched === false);
  myApplicationState.fetchSomeData();

  await tryHard(() => {
    assert(myApplicationState.dataIsFetched === true);
  });
});

Very useful also when testing the DOM, here an example with Enzyme:

it('updates the DOM', async () => {
  assert(wrapper.find('ListOfItems').length === 0);
  myReduxStore.dispatch(fetchTheItems());

  await tryHard(() => {
    assert(wrapper.find('ListOfItems').length === 10);
  });
});

Old school promises also work of course :

it('updates the application state', (done) => {
  assert(myApplicationState.dataIsFetched === false);
  myApplicationState.fetchSomeData();

  tryHard(() => {
    assert(myApplicationState.dataIsFetched === true);
  }).then(() => done()).catch(err => done(err));
});

Prerequisites

You can require directly the function in src/index.js if you are in a ES2016 environment that support async/await (or if you use Babel)

Otherwise don't forget to include regenerator-runtime:

npm install --save regenerator-runtime

And then in your entry-point:

require('regenerator-runtime/runtime');