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

all-other-things-being-equal

v1.1.1

Published

Indispensable helpers for common test cases when building web apps.

Downloads

12

Readme

Very frequently, when building and testing web applications, a developer wants to know some things about the environment in which their application will run. Will the network be reliable? Will there be infinite bandwidth, perhaps? All other things being equal, everything should work. Will all other things remain equal?

The assertions in these helpers offer a perfect simulation of a production environment for a JavaScript application, in Node or in the browser! They are compatible with every testing library and they are guaranteed to be accurate in all cases.

Installation

npm install all-other-things-being-equal.

Use the installed NPM package in Node or a CommonJS environment by calling require('all-other-things-being-equal'). In the browser, in the absence of any module loader or build system, use the dist/browser.js file:

<script src="node_modules/all-other-things-being-equal/dist/browser.js"></script>

This script will expose the global allOtherThingsBeingEqual object.

Usage

Use these helpers in your unit and integration tests. Here's a fine example:

const assert = require('assert');
const allOtherThingsBeingEqual = require('all-other-things-being-equal');

assert.ok(allOtherThingsBeingEqual.networkIsReliable());

assert.ok(allOtherThingsBeingEqual.networkIsSecure());

assert.ok(allOtherThingsBeingEqual.latencyIsZero());

assert.ok(allOtherThingsBeingEqual.bandwidthIsInfinite());

assert.ok(allOtherThingsBeingEqual.codeCoverageEqualsTestCaseCoverage());

assert.ok(allOtherThingsBeingEqual());

This is a great starting test plan right here. You can either write your code to target environments where these assertions pass, or redesign your system to not rely on these assumptions. Whichever's easier!