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 🙏

© 2026 – Pkg Stats / Ryan Hefner

gherkin-karma-example

v0.0.4

Published

Example of integrating Gherkin into karma through the help of yadda.

Readme

1. Introduction

This package is an example of an workflow for automated unit testing in JavaScript. It's goal is to support developers in improving the quality of their software.

2. Motive

Recurring problems:

Sometimes programmers are faced with one ore more of the following points:

  • Lack in motivation and time for:
    • documentation
    • unit tests
  • Costumer requirements are:
    • alternating fast
    • unclarified
    • being misunderstood

Solution:

Get everything together in one automated workflow by combining the styles of TDD and BDD.

It all starts with writing software requirements in a simple language restricted to just some keywords. Besides functioning as a fundament for documentation, they can be used as a source for automatic generated unit tests. This way the written requirements can be understood by everybody, one could even write them together with costumers or none developer co-workers. Furthermore a generated test not only saves time, it guarantees that the specified statements of the unit tests are based strictly on your requirements. As a result you minimize the risk of misconceptions. If there's a change of requirements the portrayed process chain can even be used to update the generated unit tests immediately. Since only one source is used as a fundament it's easy to keep everything consistently.

Implemented with a composition of modern frameworks this package tries to be a useful approach of the portrayed procedure.

3. Install

npm install gherkin-karma-example

4. Execute

npm test

5. Composition

Most important parts are (order is based on process chain):

infographic

6. Todo

  • Handling of gherkin feature context
  • Yeoman Integration
  • Include German words for Gherkin
  • ES6 Support
  • Include karma module CodeFlower
  • Include karma module SonarQube

Maintainer

kaasbaardje

License

MIT