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 🙏

© 2026 – Pkg Stats / Ryan Hefner

sf-delta-tests

v0.2.3

Published

Calculate dependencies and scope to relevant tests

Readme

sf-delta-tests

Calculate dependencies and scope to relevant tests.

NPM Downloads/week License

This plugin is designed to optimize your Salesforce CI/CD pipeline by calculating only the relevant test classes that need to be run based on the metadata changes in your package. It uses the Salesforce Dependency API to determine these relationships.

Install

sf plugins install sf-delta-tests

Build

To build the plugin locally, make sure to have yarn installed and run the following commands:

# Install the dependencies and compile
yarn && yarn build

To use your plugin, run using the local ./bin/dev.js or ./bin/dev.cmd file.

# Run using local run file.
./bin/dev.js delta test-classes -o <alias name> --package-path=test/fixtures/manifest/package.xml

There should be no differences when running via the Salesforce CLI or using the local run file. However, it can be useful to link the plugin to do some additional testing or run your commands from anywhere on your machine.

# Link your plugin to the sf cli
sf plugins link .
# To verify
sf plugins

Commands

sf delta test-classes

Run only related tests

USAGE
  $ sf delta test-classes -o <value> [--json] [--flags-dir <value>] [-p <value>] [--always-run-test <value>...]
    [--include-all-flows]

FLAGS
  -o, --target-org=<value>          (required) The org you want to check the dependencies against.
  -p, --package-path=<value>        [default: manifest/package.xml] Path to the package.xml that will be deployed.
      --always-run-test=<value>...  A test class to run when no tests need to be ran.
      --[no-]include-all-flows      When enabled, if any Flow is changed, include all Flows that require test coverage
                                    based on their trigger type or process type. This ensures proper test coverage
                                    validation since Salesforce checks coverage for all such Flows during deployment,
                                    not just the changed ones. Use --no-include-all-flows to disable.

GLOBAL FLAGS
  --flags-dir=<value>  Import flag values from a directory.
  --json               Format output as json.

DESCRIPTION
  Run only related tests

  Calculates the tests needed to be ran based on the changed metadata given using the Salesforce Dependency API. For
  Flows, also queries FlowTestCoverage to include test classes that have previously covered the Flows.

EXAMPLES
  testCmd=$(sf delta test-classes --target-org [email protected])

    $ sf project deploy validate ${testCmd}

sf delta test-classes

Calculates the tests needed to be run based on the changed metadata given using the Salesforce Dependency API

Run only related tests

USAGE
  $ sf delta test-classes -o <value> [--json] [--flags-dir <value>] [-p <value>] [--always-run-test <value>...] [--include-all-flows]

FLAGS
  -o, --target-org=<value>          (required) The org you want to check the dependencies against.
  -p, --package-path=<value>        [default: manifest/package.xml] Path to the package.xml that will be deployed.
      --always-run-test=<value>...  A test class to run when no tests need to be ran.
      --[no-]include-all-flows      When enabled, if any Flow is changed, include all Flows that require test coverage based on their trigger type
                                    or process type. This ensures proper test coverage validation since Salesforce checks coverage for all such
                                    Flows during deployment, not just the changed ones. Use --no-include-all-flows to disable.

GLOBAL FLAGS
  --flags-dir=<value>  Import flag values from a directory.
  --json               Format output as json.

DESCRIPTION
  Run only related tests

  Calculates the tests needed to be ran based on the changed metadata given using the Salesforce Dependency API

EXAMPLES
  testCmd=$(sf delta test-classes --target-org [email protected])

    $ sf project deploy validate ${testCmd}