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

karma-cucumber-reporter

v1.0.4

Published

Reporter that transforms test results from Karma to Cucumber format

Downloads

32,870

Readme

Karma Cucumber Reporter

Transforms Karma test output to Cucumber format which can be postprocessed by cucumber-reporting.

Installation

npm i -D karma-cucumber-reporter

Usage

Tests have to be written with a specific syntax to be recognized and translated correctly.

describe('PREFIX FEATURE', function () {
  describe('SCENARIO A', function () { //... });

  describe('SCENARIO A', function () { //... });
});
  1. The test is only included if the PREFIX string matches with the prefix option.

  2. There always have to be at least one scenario, i.e. an inner describe block.

Configuration

// karma.conf.js
module.exports = function(config) {
  config.set({
    reporters: ['cucumber'],
  });
};

If you use multiple plugins, you have to add karma-cucumber-reporter as well:

plugins: [
  // ...
  require('karma-cucumber-reporter'),
],

Options

out

Type: String

File location to write to. Defaults to stdout if not present.

// karma.conf.js
module.exports = function(config) {
  config.set({
    reporters: ['cucumber'],
    cucumberReporter: {
      out: './cucumber.json'
    }
  });
};

prefix

Type: String

Prefix which indicates that a test should be include in the report.

// karma.conf.js
module.exports = function(config) {
  config.set({
    reporters: ['cucumber'],
    cucumberReporter: {
      prefix: 'XYZ'
    }
  });
};

Example

For an example, please have a look at the examples folder. It will produce a report like this when you run npm test: