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

cucumberjs-jira-formatter

v1.0.0

Published

Interacts with ZAPI and JIRA API to report on Zephyr test status

Downloads

8

Readme

Test Reporter

JavaScript JIRA/Zephyr test reporter. To use you need to create a .env file in the root of the project including the following mandatory and optional variables.

The library is designed to have the reporter_development_version set and not the execution, cycle or version. If using semantic version you place the development version, e.g. 0.0.0-sematic-version, as the development version. This will report the name of the project as the cycle name and execution and version as ad hoc and unscheduled respectively. For the release branch, generally master, the library will search for the current version based on the start date of the version.

Example of how to tag the Zephyr tests can be found in the component-tests folder. The example project was CUC.

Mandatory elements

reporter_username=
reporter_password=
reporter_host=
reporter_port=
reporter_protocol= (http or https)
reporter_development_version=
reporter_prefix=

Optional elements

reporter_execution= (default -1)
reporter_cycle= (default 'Ad hoc'),
reporter_version= (default 'Unscheduled'),
reporter_development_version=