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

gpc-scenario-numbering

v1.0.1

Published

This GherKing precompiler is responsible to add an index to all scenario and scenario outlines.

Downloads

8,660

Readme

gpc-scenario-numbering

Downloads Version@npm Version@git CI Docs

The ScenarioNumbering precompiler is responsible for adding an index to all scenarios and scenario outlines.

Example

  @tag1
  Scenario Outline: Test language (<language>)
    Given I am on Home page <language> user
    When <language> language is choosen
    Then I should be on Home page
    And the title should be "<title>"

  @tag2
  Examples:
    | language | title     |
    | EN       | Welcome   |
    | FR       | Bienvenue |

  Scenario: Test without tag
    Given I am on Home page user
    Then I should be on Home page

It will be modified to:

  @tag1
  Scenario Outline: 1. Test language (<language>)
    Given I am on Home page <language> user
    When <language> language is choosen
    Then I should be on Home page
    And the title should be "<title>"

  @tag2
  Examples:
    | language | title     |
    | EN       | Welcome   |
    | FR       | Bienvenue |

  Scenario: 2. Test without tag
  Given I am on Home page user
  Then I should be on Home page

Configuration

ScenarioNumbering accepts the following configuration:

| Option | Type | Description | Default | |:------:|:----:|:------------|:--------| | format | String | The format, how index should be added to the name of the scenario/scenairo outline. Possible tokens: ${name} the original name${i} the index | ${i}. ${name} |

Other

This package uses debug for logging, use gpc:scenario-numbering :

DEBUG=gpc:scenario-numbering* gherking ...

For detailed documentation see the TypeDocs documentation.