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

gherkin-parse

v1.0.12

Published

NPM package for converting a .feature(cucumber framework) file to a JSON file and vice versa.

Downloads

68,800

Readme

HitCount Say Thanks!

forthebadge forthebadge

gherkin-parse

gherkin-parse is an NPM package designed to convert .feature files, commonly used in Cucumber test cases, into JSON objects and vice versa.

Installation

npm i gherkin-parse

Usage

const parser = require("gherkin-parse");

const jsonObject = parser.convertFeatureFileToJSON("./sample.feature");

const featurefile = parser.convertJSONToFeatureFile(jsonObject);

Example

Consider the following sample feature file:

@tag1 @tag2
Feature: Hello world Before Edit
    this is a feature description

    @tag2 @tag3
    Scenario: this is a scenario 1
        Given this is a data
        And this is a given step too
        When this is a when step
        And this is a when step too
        Then it should be a then step
        And it should be a then step too

The JavaScript object returned by convertFeatureFileToJSON would be:

{
  "type": "GherkinDocument",
  "feature": {
    "type": "Feature",
    "tags": [
      { "name": "@tag1" },
      { "name": "@tag2" }
    ],
    "location": { "line": 2, "column": 1 },
    "language": "en",
    "keyword": "Feature",
    "name": "Hello world Before Edit",
    "description": "    this is a feature description",
    "children": [
      {
        "type": "Scenario",
        "tags": [
          { "name": "@tag2" },
          { "name": "@tag3" }
        ],
        "name": "this is a scenario 1",
        "steps": [
          { "keyword": "Given", "text": "this is a data" },
          { "keyword": "And", "text": "this is a given step too" },
          { "keyword": "When", "text": "this is a when step" },
          { "keyword": "And", "text": "this is a when step too" },
          { "keyword": "Then", "text": "it should be a then step" },
          { "keyword": "And", "text": "it should be a then step too" }
        ]
      }
    ]
  },
  "comments": []
}

This JSON object can be used for further processing and modifications. You can convert it back into a feature file string using convertJSONToFeatureFile. This string can then be written back to a .feature file using Node's fs module.

@tag1 @tag2
Feature: Hello world After Edit
    this is a feature description

    @tag2 @tag3
    Scenario: this is a scenario 1
        Given this is a data
        And this is a given step too
        When this is a when step
        And this is a when step too
        Then it should be a then step
        And it should be a then step too