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

cucumber-for-jenkins

v0.5.3

Published

The unofficial JavaScript implementation of Cucumber.

Downloads

33

Readme

This is a project based on Cucumber.js found at https://www.npmjs.com/package/cucumber and is only meant to be used alongside the project found there.

The purpose of this package is to save a JSON file of the cucumber report under the name output.json inside the Jenkins workspace to be used in generating cucumber reports.

I simply exchanged the process.stdout.write( data ) with a require('fs').writeFileSync('output.json', data, {encoding: 'utf-8'} ) when the JENKINS_HOME environment variable is present, all other functionality of cucumber is left alone and is taken from version 0.5.2. This should cause all the reports inside of Jenkins to be printed to output.json and all local implementation to be left alone.

I also added a callback.skip() Before there was only callback.pending() and callback.fail() but since our tests are relying on outside services I want the tests to skip and not fail if the services are not running or timing out ( you might argue that any external calls should be mocked but there are reasons against that in our case ). Use callback.skip() however you want, or choose not to! That's just why I included it in this latest version.

USAGE:

$ npm install cucumber-for-jenkins

only use this inside of Jenkins, use cucumber-js for all local development, and only use the json format, as other formats will just be written to a file and not do you much good.

to run this in shell on Jenkins use the command

node node_modules/.bin/cucumber-js -f json

skipping a step in cucumber

    callback.skip();

All functionality is kept from cucumber-js so all the tags and scenario outlines and whatever other cool functionality you enjoy in version 0.5.2 is maintaned. Once the feature test has completed, then check into your Jenkins workspace folder and you will find output.json in the root level.

Enjoy!

Contact