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

jasmine-stray-timers

v1.1.0

Published

Jasmine test helper for detecting setTimeout and setInterval usage outside of test boundaries

Downloads

70

Readme

jasmine-stray-timers npm Build Status

Jasmine test helper for detecting setTimeout and setInterval usage outside of test boundaries.

Requires jasmine.

Install

$ npm install --save-dev jasmine-stray-timers

Usage

In karma:

// karma.conf.js
module.exports = function(config) {
  config.set({
    frameworks: ['jasmine'],

    files: [
      // ...,
      require.resolve('jasmine-stray-timers'),
      // ...
    ],
  });
};

Ignoring stray timers in a test

Stray timers can be ignored in a single test or in a suite by calling this._ignoreStrayTimers in the jasmine test context.

export function foo(a) {
  setTimeout(function() {
    // do something async
  }, 100);
  return a + 1;
}

describe('foo', function() {
  it('bar', function() {
    this._ignoreStrayTimers();

    expect(bar()).toEqual(2);
  });
});

Only print warning on stray timers in a test

Stray timers can be ignored, and an error can be printed in a single test or in a suite by calling this._onlyWarnOnStrayTimers in the jasmine test context.

export function foo(a) {
  setTimeout(function() {
    // do something async
  }, 100);
  return a + 1;
}

describe('foo', function() {
  it('bar', function() {
    this._onlyWarnOnStrayTimers();

    expect(bar()).toEqual(2);
  });
});

Output

If test code executed a timer and didn't wait for it to resolve before ending the test, it will throw an error.

// src.js
export function foo(a) {
  setTimeout(function() {
    // do something async
  }, 100);
  return a + 1;
}

export function bar() {
  return foo(1);
}
// test.js
import { bar } from './src';

describe('foo', function() {
  it('bar', function() {
    expect(bar()).toEqual(2);
  });
});
PhantomJS 2.1.1 (Mac OS X 0.0.0) foo bar FAILED
       Error: Stray "setTimeout" call was executed outside the test constraints (line 68)
       localSetTimeout
       foo
       bar
       loaded@http://localhost:9876/context.js:151:17
PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 1 of 1 (1 FAILED) (skipped 10) ERROR (0.005 secs / 0.001 secs)

Caveat

Due to the nature of how async javascript execution works, if a timer is set up within another async operation (eg. Promise), this library cannot reliably determine the exact test that triggered the timer.

In this case, the error will be triggered in an subsequent test in which the async operation resolved.

// src.js
export function foo(a) {
  window.fetch('some url')
    .then(function() {
      setTimeout(function() {
        // do something async
      }, 100);
    });
  return a + 1;
}
// test.js
import './src';

describe('foo', function() {
  it('test 1', function() {
    expect(foo(1)).toEqual(2);
  });

  it('test 2', function() {
    expect(2).toEqual(2);
  });
});

License

Apache-2.0