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 🙏

© 2025 – Pkg Stats / Ryan Hefner

combotest

v1.1.10

Published

A testing utility for exhaustively testing combinations of variables. Makes it easy to define expected outcomes, and generates a nice, easy-to-read table of results.

Readme

Combotest

A testing utility for exhaustively testing combinations of variables. Makes it easy to define expected outcomes, and generates a nice, easy-to-read table of results.

Combotest is primarily designed for use cases where you have many combinations of variables but only a small set of distinct outcomes. A common use case for this would be to determine which users have access to a given feature. It might be conditional based on roles, feature flags, product tiers, or any other internal logic. As a counterexample, you wouldn't necessarily want to use it for something like testing an addition function where every combination of inputs may produce a distinct output.

For example, let's say you want to test this simple function:

type User = {
  role: string;
};

function isAllowed({ user, feature }: { user: User; feature: boolean }) {
  return user.role === "admin" || feature;
}

Here's how you would use combotest to ensure it works correctly for all combinations of values:

// define your inputs as `dimensions`
const role = createDimension({
  header: "Role",
  values: ["admin", "user", "readonly"],
  apply: (value, context: { user: User }) => {
    context.user.role = value;
  },
});

const feature = createDimension({
  header: "Feature Enabled",
  values: [false, true],
  apply: (value, context: { feature: boolean }) => {
    context.feature = value;
  },
});

// create the matrix of possible outcomes
const outcomeMatrix = new TestOutcomeMatrix({
  dimensions: { role, feature },
  outcomes: ["allowed", "notAllowed"],
  defaultOutcome: "notAllowed",
});

// define the non-default outcomes you expect
outcomeMatrix.defineOutcomes(({ role, feature }) => {
  if (role === "admin" || feature) {
    return "allowed";
  }
});

// write your test cases tailored to your custom outcomes
outcomeMatrix.testOutcomes((applyDimensions, outcome) => {
  // this will call the `apply` function for every combination of dimension values
  // provide some defaults to satisfy typescript, these attributes will be overwritten
  const context = applyDimensions({ user: { role: "admin" }, feature: false });

  // you can do whatever you want here, but this is a nice pattern for defining your tests
  const { message, assertion } = {
    allowed: {
      message: "is allowed",
      assertion: () => expect(isAllowed(context)).toBe(true),
    },
    notAllowed: {
      message: "is not allowed",
      assertion: () => expect(isAllowed(context)).toBe(false),
    },
  }[outcome];

  it(message, () => {
    // you can put shared test setup here

    // then call your outcome-specific assertion
    assertion();
  });
});

This will generate the following tests:

 ✓ src/feature-access.test.ts (7 tests) 2ms
   ✓ Role     | Feature Enabled > Outcome 1ms
   ✓ admin    | false           > is allowed 0ms
   ✓ admin    | true            > is allowed 0ms
   ✓ user     | true            > is allowed 0ms
   ✓ readonly | true            > is allowed 0ms
   ✓ user     | false           > is not allowed 0ms
   ✓ readonly | false           > is not allowed 0ms

 Test Files  1 passed (1)
      Tests  7 passed (7)

If, for example, the logic changed to user.role === "admin" && feature, you would see these failures:

 ❯ src/feature-access.test.ts (7 tests | 3 failed) 6ms
   ✓ Role     | Feature Enabled > Outcome 1ms
   × admin    | false           > is allowed 4ms
     → expected false to be true // Object.is equality
   ✓ admin    | true            > is allowed 0ms
   × user     | true            > is allowed 1ms
     → expected false to be true // Object.is equality
   × readonly | true            > is allowed 0ms
     → expected false to be true // Object.is equality
   ✓ user     | false           > is not allowed 0ms
   ✓ readonly | false           > is not allowed 0ms

To fix it, you would update your test to:

outcomeMatrix.defineOutcomes(({ role, feature }) => {
  if (role === 'admin' && feature) {
    return 'allowed';
  }
});

And you would see this output:

 ✓ src/feature-access.test.ts (7 tests) 2ms
   ✓ Role     | Feature Enabled > Outcome 1ms
   ✓ admin    | true            > is allowed 0ms
   ✓ admin    | false           > is not allowed 0ms
   ✓ user     | false           > is not allowed 0ms
   ✓ user     | true            > is not allowed 0ms
   ✓ readonly | false           > is not allowed 0ms
   ✓ readonly | true            > is not allowed 0ms

 Test Files  1 passed (1)
      Tests  7 passed (7)