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

wct-istanbub

v0.2.10

Published

Instanbuljs coverage reporting for projects being tested by web-component-tester

Downloads

333

Readme

WCT-istanbub

Istanbul coverage plugin for web-component-tester.

Use this plugin to collect and report test coverage (via istanbul) for your project on each test run.

In order to use this coverage plugin use at least version 6.4.0 of web-component-tester

Check out this test repository for an example with 'app' and travis build

Installation

npm install wct-istanbub --save-dev

Basic Usage

Add the following configuration to web-component-tester's config file.

Example

module.exports = {
  plugins: {
    istanbub: {
      reporters: ["text-summary", "lcov"],
      include: [
        "**/*.html"
      ],
      exclude: [
        "**/test/**"
      ]
    }
  }
}

Options

Below are the available configuration options:

reporters

An array of istanbul reporters to use.

include

Files to include in instrumentation, default the basepath will be added - /components/${packagename}/{includepaths}

exclude

Files to exclude from instrumentation (this trumps files 'included' with the option above).

By default the '/test/' is excluded as istanbub crashes on some of the test tooling used by most projects and testing the coverage of your test files is not really useful.

default the basepath will be added - /components/${packagename}/{excludepaths}

configFile

Path to an Istanbul configuration file.

configOverrides

Overrides for the default Istanbul configuration. Check the default configuration for all available options.

ignoreBasePath

Don't add the basepath to the include & exclude array's for specific use-cases

npm

Support for npm based on where to retrieve basic assets from node_modules instead of bower_components

moduleResolution

Define support module import (node) or none, allowed values: node and none

Defaults to none if npm false or node if npm is true

isComponentRequestOverride

Override the componentRequest check

babelPlugins

Add babel plugins to default set: [importMeta, asyncGenerators, dynamicImport, objectRestSpread, optionalCatchBinding, flow, jsx], for example [dotallRegex]. Duplicates will be filtered out

Coverage Thresholds

In addition to measuring coverage, this plugin can be used to enforce coverage thresholds. If coverage does not meet the configured thresholds, then the test run will fail, even if all tests passed.

This requires specifying the thresholds option for the plugin

writeOnlyOnSuccess false

Set to true to write coverage only if all tests pass

Example

The following configuration will cause the test run to fail if less than 100% of the statements in instrumented files are covered by tests.

module.exports = {
  plugins: {
    istanbub: {
      dir: "./coverage",
      reporters: ["text-summary", "lcov"],
      include: [
        "**/*.html"
      ],
      exclude: [
        "**/test/**"
      ],
      thresholds: {
        global: {
          statements: 100
        }
      }
    }
  }
}