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

verify-junit-xml

v0.0.3

Published

Verifies that JUnit XML describes a successful test run

Downloads

11,524

Readme

Verifies that JUnit XML describes a successful test run. This is useful if, for example, you want to run unit tests in Maven's integration-test phase and verify their output in the verify phase.

Running tests

Assuming you have npm installed, run the following in the verify-junit-xml directory:

$ npm install
$ npm install --global gulp
$ gulp test

Usage

Command line

The verify-junit-xml script takes one or more paths to JUnit XML files and verifies that they all describe successful test runs. If any file reports errors or failures the script logs to stderr and exits with status code 1.

$ npm install -g verify-junit-xml

$ verify-junit-xml --help
Usage: verify-junit-xml file [file ...]

# A successful test run
$ verify-junit-xml successful.xml
$ echo $?
0

# An unsuccessful test run
$ verify-junit-xml unsuccessful.xml
The JUnit XML file "unsuccessful.xml" describes an unsuccessful test run
$ echo $?
1

# An invalid JUnit XML file
$ verify-junit-xml invalid.xml
Couldn't verify the JUnit XML file "invalid.xml"

# Multiple files
$ verify-junit-xml successful.xml also-successful.xml
$ echo $?
0

Node module

The verify-junit-xml node module exports a custom error class and two functions, both returning Bluebird promises.

UnsuccessfulError

A custom error class that is used to indicate an unsuccessful test run as opposed to, e.g. failure to read a JUnit XML file. See the example below.

verifyFile(path) -> Promise

Verify that the JUnit XML file at the specified path describes a successful test run. The returned promise is resolved on success, rejected with an UnsuccessfulError if it describes an unsuccessful test run, and rejected with no error on failure (e.g. can't read the file).

var junitXml = require('verify-junit-xml');

junitXml.verifyFile('results.xml').then(function () {
  // Success
}).catch(junitXml.UnsuccessfulError, function () {
  // Test errors or failures
}).catch(function () {
  // Unknown error
});

verifyXml(xml) -> Promise

Verify that the given JUnit XML describes a successful test run. The promise is rejected / resolved in the same way as verifyFile.