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

will-call

v1.0.1

Published

check that expected function calls are actually made

Downloads

67,435

Readme

will-call

Current Version Build Status via Travis CI Dependencies

belly-button-style

Credit: This module borrows heavily from the common.mustCall() functionality in Node core's test suite.

will-call allows you to mark functions that should be executed. You can later check which functions were actually called.

const WillCall = require('will-call');
const wc = new WillCall();
const foo = wc.expect(function foo () { return 'foo'; });     // must be called once
const bar = wc.expect(function bar () { return 'bar'; }, 2);  // must be called twice
const baz = wc.expect(function baz () { return 'baz'; });     // must be called once

foo();
bar();
baz();
baz();

const results = wc.check();
// results contains an array of length two, corresponding to bar() and baz()
// Each entry provides the function name, a stack, expected calls, and actual calls

Methods

will-call exports a constructor function that takes no arguments. Constructed instances support the following methods.

WillCall.prototype.expect(fn [, expected])

  • Arguments
    • fn (function) - The function that is expected to be called.
    • expected (integer) - The exact number of times that fn should be called. If a non-negative integer is not received, this defaults to 1. Optional.
  • Returns
    • A wrapped version of fn. The wrapped function should behave the same as fn.

This function specifies the exact number of times that a given function is expected to be called. expect() returns a wrapped version of the fn argument. It is important that the wrapped function be used instead of the original fn function.

WillCall.prototype.check()

  • Arguments
    • None
  • Returns
    • Array of objects. Each object adheres to the following schema.
      • name (string) - The name of the function, or '<anonymous>' if the function doesn't have a name.
      • expected (integer) - The number of times the function was expected to be called.
      • actual (integer) - The number of times the function was actually called.
      • stack (string) - A partial stack trace identifying where the function was passed to expect().

This function verifies that all expected functions were called the correct number of times. check() returns an array identifying the functions that were not called correctly. This function does not alter any internal state, and can be called multiple times.