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

qunit-junit

v1.0.0

Published

Produce JUnit-style XML test reports with QUnit.

Downloads

26

Readme

JUnit Reporter for QUnit

A QUnit plugin that produces JUnit-style XML test reports (e.g. for integration into build tools like Jenkins).

Usage

New API

Include the plugin script ("qunit-reporter-junit.js") after the QUnit core script itself, then register callback(s) using jUnitDone to do something with the XML string (e.g. upload it to a server):

QUnit.jUnitDone(function(report) {
  if (typeof console !== 'undefined') {
    console.log(report.xml);
  }
});

With this new API (as of v1.1.0), you can even register a callback after the tests have finished and still successfully receive the data (so long as the "qunit-reporter-junit.js" script was included before the test run began).

Old API

The old API approach of implementing the jUnitReport hook is also still supported:

QUnit.jUnitReport = function(report) {
  if (typeof console !== 'undefined') {
    console.log(report.xml);
  }
};

With this old API, you MUST implement the callback before the tests have finished or else you will never receive the data.

Notes

If you're using Grunt, you should take a look grunt-contrib-qunit.