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

create-junit-report

v1.1.0

Published

Creates a JUnit XML file based on the provided input parameters

Downloads

4,205

Readme

create-junit-report Build Status

Creates a JUnit XML file based on the provided input parameters.

Can be used to create a JUnit XML file from command line, e.g. from a shell script's results. This is great for continuous integration, in case you're running some test steps that don't provide their own JUnit-compatible reporter.

Install

$ npm install --save create-junit-report

Usage

const createJunitReport = require('create-junit-report');

createJunitReport('suite', 'class', 'test', false, 'Foo Bar Baz', { outputPath: 'foo' });
//=> creates `foo/suite.xml` file

The generated foo/suite.xml file looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
  <testsuite name="suite">
    <testcase classname="class" name="test">
      <failure message="Foo Bar Baz"/>
    </testcase>
  </testsuite>
</testsuites>

API

createJunitReport(suiteName, className, testName, passed, failureMessage, [options])

suiteName

Type: string

Name of the test suite, also the name of the generated file (+ .xml). Mandatory parameter.

className

Type: string

Used for the result file's classname attribute of the testcase entry. Mandatory parameter.

testName

Type: string

Used for the result file's name attribute of the testcase entry. Mandatory parameter.

passed

Type: boolean

Used to indicate test success (truthy) or test failure (falsy).

failureMessage

Type: string

Optional failure message in case of a test failure.

options

outputPath

Type: string
Default: .

Output directory of the generated file.

CLI

$ npm install --global create-junit-report
$ create-junit-report --help

  Usage
	 $ create-junit-report [suite] [class] [test] [passed] [failureMessage]

  Options
	 --outputPath  path [Default: .]

  Examples
	 $ create-junit-report suite class test 1 --outputPath foo
		 ==> creates `foo/suite.xml`

License

MIT © Nils Winkler