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

promise-to-test

v0.0.5

Published

simple set of tools for making things you probably shouldn't do in tests seem nicer. Such as waiting (setInterval) for things to complete, and waiting before continuing actions (setTimeout). Very promise focused, depends on Q.

Downloads

1

Readme

promise-to-test

Simple set of utils for making async tests more sane using promises.

Reasoning

I found myself writing some really awful code because I wanted to wait for something to happen, but I did not want to hook into the particular methods causing it. I.e., I wanted my test to act like a user, just keep checking and give up after a certain amount of time. It looked like this :

var it = setInterval(function(){
  if($('myCondition').length>0) {
    clearInterval(it)

    // carry on testing

    done()
  }
}, 10)

This didn't make me happy, and it was actually nested two or three levels deep, which I'll let you imagine. Apart from aesthetics, this approach also doesn't give much information when it does time out, and we're abandoning all the lovely assertion techniques at our disposal for the condition.

If we rewrite this code using my new tools (ok, just waitFor), it looks like this :

waitFor(function(){
  assert.ok($('myCondition').length>0)
})
.then(function(){
  // carry on testing
})
.then(function(){done()}, done)

So this is actually a similar amount of code, but...

  • code reads chronologically top to bottom
  • we use a real assertion and pass an assertion error on failure
  • nesting / waiting again will not bother me at all, things will extend downward, not rightward

API

waitFor(condition, timeout, frequency)

  • condition : a function using assertions to test for something
  • timeout : optional, the amount of time to wait before failing, defaults to 1000 milliseconds
  • frequency : optional, the amount of time to wait before checking again, defaults to 10 milliseconds

Runs the condition function every frequency milliseconds until either condition runs without errors or timeout milliseconds have passed. Returns a promise that resolves if condition runs without errors and rejects with the last error thrown by condition if timeout is reached.

justWait(timeout)

  • timeout : the amount of time to wait for (duh)

Returns a promise which will resolve in timeout milliseconds.

See Also

chai-as-promised and mocha-as-promised are both wonderful ways to clean up async tests with promises, you can even avoid the nasty .then(function(){done()}, done) at the end of your promise chain!