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

runas-recipe-unit-testing

v0.3.0

Published

Unit testing for the recipe context. Include coverage validation

Downloads

3

Readme

runas Recipe runas-recipe-unit-testing

Unit testing with coverage for recipes and npm-libraries. Using mocha (default) and nyc for the matter.

  1. Description
  2. Configuration
  3. More information

Description

Step for recipe and npm-library contexts. It will run the tests configured in the repo and will calculate the coverage of such test suites. It will check the thresholds for this repo in particular.

We will be able to configure our recipe parameters as usual, in our piscosour.json file. But we also can configure it in the package.json or in a .nycrc file. All the documentation in this link

Configuration

Example:

{
  "test-runner-nyc": {
    "ignoreErrors": true,
    "config": {
      "_": [
        "npm",
        "test"
      ],
      "all": true,
      "reportDir": "test-reports",
      "reporter": [
        "text-summary",
        "lcov",
        "html"
      ],
      "exclude": [
        "node_modules",
        "*-test.js",
        "test-reports/**",
        "test/**"
      ],
      "checkCoverage": true,
      "statements": 70,
      "branches": 70,
      "functions": 70,
      "lines": 70
    }
  }
}

Where:

| Param | Type | Default | Description | | --- | --- | --- | --- | | _ | Array | ["npm", "test"] | Execution for the unit tests in the recipe | | all | Boolean | true | Include all the files in the coverage report | | reportDir | String | "test-reports" | Directory where the reports are stored | | reporter | Array | ["text-summary", "lcov", "html"] | Reports generated | | exclude | Array | ["node_modules", "*-test.js", "test-reports/", "test/"] | Files excluded | | checkCoverage | Boolean | true | Check for the coverage thresholds | | statements | Integer | 70 | Threshold for staments percent coverage | | branches | Integer | 70 | Threshold for branches percent coverage | | functions | Integer | 70 | Threshold for functions percent coverage | | lines | Integer | 70 | Threshold for lines percent coverage |

More information:

  • Contexts: "recipe", "npm-library"
  • Plugins: "test-runner-istanbul"