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

mocha-junit

v0.4.0

Published

Write junit compatible results file

Downloads

4

Readme

This Module can be loaded via mocha --require. It is only activated if process.env.REPORT_FILE is set. If activated, it:

  • writes a junit-compatible xml-report to the file denoted in process.env.REPORT_FILE
  • captures all stdout/stderr from tests and redirects them to this report
  • sets mocha exit code to zero, if test results are written successful

Hook Behaviour

If a Mocha hook fails, the hook is counted as one failure, and mocha behaves as follows:

  • before all: all tests in the block are ignored
  • after all: all tests have their normal results
  • before each: the remaining tests are ignored
  • after each: the remaining tests are ignored

To keep the number of tests constant, this behavior is changed:

  • before all: first test in block fails with the hook failure, remaining tests are pending
  • after all: last test in block fails with the hook failure
  • before each: next test fails with the hook failure, remaining tests are pending
  • after each: last test fails with the hook failure, remaining tests are pending