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

can-test-helpers

v1.1.4

Published

Test utilities for CanJS modules

Downloads

4,237

Readme

can-test-helpers

Join our Slack Join our Discourse License: MIT npm version Travis build status Greenkeeper badge

Common utilities for effectively testing the features of CanJS.

Documentation

dev.willWarn(expected, [fn])

Requests that canDev.warn track and notify about matching warnings.

  • expected: {String|Regexp} expected The warning message to check for
  • fn: {Function(String, Boolean)} [fn] an optional callback to fire on every warning; each call has the actual warning message and a Boolean indicating whether it was matched.

Returns a function that tears down the warning check and returns the number of matched warnings when called.

willWarn() takes either a String or a RegExp as its expected warning, and does a full, case-sensitive String match in the case of a String, or a regex test in the case of a RegExp, for every warning logged through [can-log/dev/dev.warn]. In addition, if fn is provided, it is fired on every warning with the content of the warning message and whether it matched expected.

willWarn() returns a teardown function, which must be called at least once to disable the tracking of the matched warning. when called, the teardown function returns the number of times expected was matched by a dev warning.

import dev from "can-log/dev/dev";
import devHelpers from "can-test-helpers/lib/dev";

const finishWarningCheck = devHelpers.willWarn( "something evil", function( message, match ) {
	message; // -> "something evil"
	match; // true
} );

canDev.warn( "something evil" );

finishWarningCheck(); // -> 1

dev.willError(expected, [fn])

Requests that [can-log/dev/dev.error canDev.error] track and notify about matching errors.

  • expected {String|Regexp} expected The error message to check for
  • fn {Function(String, Boolean)} [fn] an optional callback to fire on every error; each call has the actual error message and a Boolean indicating whether it was matched

Returns a function that tears down the error check and returns the number of matched errors when called.

willError() takes either a String or a RegExp as its expected error, and does a full, case-sensitive String match in the case of a String, or a regex test in the case of a RegExp, for every error logged through [can-log/dev/dev.error]. In addition, if fn is provided, it is fired on every error logged by dev.error with the content of the error message and whether it matched expected.

willError() returns a teardown function, which must be called at least once to disable the tracking of the matched error. when called, the teardown function returns the number of times expected was matched by a dev error.

import dev from "can-log/dev/dev";
import devHelpers from "can-test-helpers/lib/dev";

const finishErrorCheck = devHelpers.willError( "something evil", function( message, match ) {
	message; // -> "something evil"
	match; // true
} );

canDev.error( "something evil" );

finishErrorCheck(); // -> 1

dev.devOnlyTest(...)

Defines a test that runs only in development mode.

  • {Number} [waits] an optional number of async waits
  • {String} name the String identifier for the test in the test module
  • {Function} fn the function body of the test.

The parameter list above assumes that test on the global object is a QUnit test function. With devOnlyTest, the global test function will be run with the supplied parameters when the system environment is either unknown or not one of the production tests. This is to help facilitate tests that rely on, e.g., canDev behavior that only exists in development builds.

dev.devOnlyTest( "it works", function() {
	QUnit.ok( true, "it works!" );
} );

Changelog

See the latest releases on GitHub.

Contributing

The contribution guide has information on getting help, reporting bugs, developing locally, and more.

License

MIT