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

json-to-junit

v2.2.0

Published

JSON to JunitXML converter

Downloads

7,455

Readme

JSON to JUnitXML Converter

This converter is useful if you are using a Jenkins reporter that publishes a json test result but does not publish JUnitXML and hence does not display test trend data. It is currently written to work with mochawesome reporter.

It accepts parameters for the path to json files and the destination path for converted JUnitXML files. It creates the JUnitXML file with the same base name as the JSON file it is converting. There is also a jsontype optional parameter which is currently dormant until additional JSON types aside from mochawesome are incorporated.

Install

json-junit should be added to your test codebase as a dev dependency. You can do this with:

npm install --save-dev jsonjunit

or

yarn add --dev jsonjunit

Alternatively, you can manually add it to your package.json file:

{
  "devDependencies" : {
    "jsonjunit": "latest"
  }
}

then install with:

npm install --dev

or

yarn install

Run

$ node_modules/.bin/jsonjunit --json PATH_TO_JSON_DIRECTORY --junit PATH_TO_JUNITXML_DIRECTORY

where PATH_TO_JSON is a path from your current working directory to the directory containing JSON files you wish to convert, and PATH_TO_JUNITXML is a path to the directory where you wish to create the converted JUnitXML files.

All *.json files will be converted to *.xml with the same filename

DEV

Useful junit format definition https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd

License

Copyright (c) 2016 Aaron Briel
Copyright (c) 2020 Daniel Yang

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.