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

@xml-conformance-suite/mocha

v3.0.0

Published

This package provides a builder and runner for running the suite as Mocha tests.

Downloads

100

Readme

This is an adapter for running the XML conformance suite published by the W3C as part of a Mocha test suite.

Using the Adapter

There are two broad options:

  1. Execute a runner from under runners. This is generally appropriate when you want to just run XML tests in isolation from other kinds of test, and may be helpful when you are setting up or testing your XML test suite configuration. The runner will load the driver you specify and use the selection of tests you specify and will just run these tests.

  2. Build a series of tests by using a builder under builders. The builders export a build function which allows you to incorporate the conformance tests as part of larger suite.

In all cases you must specify:

  1. How to run the code under test and determine whether the test was successful or not. You do this by specifying a "driver".

  2. How to dertermine which test to run and which to skip. You do this by specifying a "selection".

Using A Runner

You need to disclose the runner to the test framework it is made for and specify the driver and selection on the command line. By convention the driver is specified using the argument --xml-driver and the selection using the argument --xml-selection.

For instance, if you want to use the Mocha runner with the xmllint driver and the xmllint selection:

$ mocha --delay [path to this package]/runners/basic.js \
  --xml-driver=@xml-conformance-suite/js/drivers/xmllint \
  --xml-selection=@xml-conformance-suite/js/selections/xmllint

The path to the runner needs to be appropriate to how you invoke your test framework. If you run mocha you must give it the path where it can find the runner in the same way you would if you asked it to run any other test file.