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

@neurodevs/node-test-counter

v1.4.7

Published

Count total number of test cases across repos

Readme

node-test-counter

Count the total number of test cases across repos

Table of Contents

Overview

node-test-counter is a lightweight utility for scanning multiple repositories and counting the number of test cases across them. It’s useful for keeping track of testing coverage across a monorepo or ecosystem of packages.

If you install the package globally, there is a CLI that you can use with a simple count-tests [...] on the command-line.

Installation

Package Installation

For basic usage within a pacakge, install node-test-counter with your preferred package manager (run inside your Node project):

npm install @neurodevs/node-test-counter

Or, for example with yarn:

yarn add @neurodevs/node-test-counter

Global Installation

node-test-counter also comes with a built-in CLI that can be installed globally so you can run it from anywhere without needing a local script. See CLI Usage section for more details.

npm install -g @neurodevs/node-test-counter

Or, with yarn:

yarn global add @neurodevs/node-test-counter

Usage

CLI Usage

Once installed globally, you can run node-test-counter directly from the command line.

If don't pass any args, it will count tests in the current working directory, with results shown for each top-level subdirectory:

count-tests

You can also pass it a list of repos to check:

count-tests path/to/repo1 path/to/repo2

Check the help message with:

count-tests --help

CrossRepoTestCounter

The counter works by recursively counting occurrences of test( in the specified repoPaths. All repositories must exist locally on your filesystem before running.

import { CrossRepoTestCounter } from '@neurodevs/node-test-counter'

async function main() {
    const instance = CrossRepoTestCounter.Create()

    const repoPaths = [
        '/path/to/repo1',
        '/path/to/repo2',
        // Add more repo paths as needed
    ]

    const result = await instance.countTestsIn(repoPaths)
    console.log(result)

    // Example output:
    // {
    //   total: 7,
    //   perRepo: {
    //     '/path/to/repo1': 3,
    //     '/path/to/repo2': 4
    //   },
    //   perRepoOrdered: Map(2) {
    //     '/path/to/repo2' => 4,
    //     '/path/to/repo1' => 3
    //   }
    // }
}

main().catch((err) => {
    console.error('Error running test counter:', err)
})