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

@padigital/pumpkin

v2.0.5

Published

Generate a test report directly from gherkin feature files. Cucumber and manual tests in blissful harmony.

Downloads

93

Readme

Pumpkin 🎃

This application generates a test report directly from your gherkin feature files, so that your scenarios can be used as tests without the need for automation with Cucumber. If you have already automated some of your scenarios, the script accepts a Cucumber report (JSON) and it will pre-selet the pass/fail status of those implemented scenarios so that you can fill in the rest manually.

Installation

$ npm install @padigital/pumpkin

Usage

Run the script as follows:

$ pumpkin --features /path/to/your/features/directory

The script accepts the following arguments:

  • --features is the path to a local directory of gherkin feature files
  • --cucumberjson is the path to a local JSON file containing a Cucumber test report (optional)
  • --reporthtml is the path to a previous pumpkin HTML report (optional)
  • --open to open the HTML report in your browser after the script completes
  • --title to set the report title
  • --date to set the report date/time
  • --notes to set the report notes
  • --exclude a space-separated list of tags to exclude e.g. "@wip @regression"

Saving your results

Pumpkin generates a single HTML file inside which you record the status of each scenario (Descoped, In Progress, Passed, Failed or Blocked). You can set the status for every scenario within a feature, or set each scenario individually. When you're finished, or you want to save your work, click the "Save HTML" button at the top. Your browser will download a new HTML file containing all of your changes. Open this file and carry on making further changes in the future.

The best way to share the report is to generate a PDF by printing it. Pumpkin has a print stylesheet that will create a nice, clean, client-friendly report.

Altering the order of features

By default the features will appear in the report in the same order that the files are ordered on your computer (alphabetically). To override this order use the @report-order-N tag on each feature. Tagged features will appear first, then the others ordered alphabetically. For example:

@report-order-1
Feature: Login
...

@report-order-2
Feature: Registration
...

Pre-populating scenario status from a Cucumber report

If you pass the path to a Cucumber test run output (--cucumberjson) the script will attempt to find the pass/fail status from this file by matching the feature and scenario names.

Pre-populating scenario status from a previous HTML report

If you pass the path to a previous HTML report generated by this script (--reporthtml), it will attempt to find the scenario status by matching the scenario name. For example:

$ pumpkin --features /path/to/your/features/directory --reporthtml /path/to/another/report.html

Example

Example report