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

@clowd/suggest-test

v0.0.1-rc.5

Published

A clover.xml parser to suggest the next unit test to write

Downloads

8

Readme

@clowd/suggest-test

Purpose

This tool is meant to automate choosing the next file for which code coverage is needed. A clover.xml is parsed to suggest the next unit test to write.

Getting Started

Add a clover test reporter

https://jestjs.io/docs/cli#--reporters

Generate a coverage report

https://jestjs.io/docs/cli#--coverageboolean

Install @clowd/suggest-test

npm i -D @clowd/suggest-test

Add a package.json script

I recommend passing these flags to focus on conditionals and fully untested files.

{
  "scripts": {
    "st": "suggest-test coverage/clover.xml --includeTested=false --includeStatements=false"
  }
}

Execute the script

npm run st

Open your favorite coverage viewer

Perhaps open coverage/lcov-report/index.html in your web browser

Tip: If you are at liberty to break a suggested file into smaller pieces and re-run the script, the re-run may point you to an even better file to test next.

Write a test

TODO: Link to opinionated unit test example.