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-composite

v2.0.0

Published

Run multiple QUnit test suite pages.

Downloads

115

Readme

Build Status NPM version

QUnit Composite

Composite is a QUnit plugin that, when handed an array of files, will open each of those files inside of an iframe, run the tests, and display the results as a single suite of QUnit tests.

The "Rerun" link next to each suite allows you to quickly rerun that suite, outside the composite runner.

If you want to see what assertion failed in a long list of assertions, just use the regular "Hide passed tests" checkbox.

Compatibility

QUnit Composite >=2.0.0 is compatible with QUnit >=1.18.0 <3.0.0.

QUnit Composite <2.0.0 (e.g. v1.2.2) is compatible with QUnit <2.0.0.

Usage

Load QUnit itself as usual plus qunit-composite.css and qunit-composite.js, then specify the test suites to load using QUnit.testSuites:

QUnit.testSuites([
    "example-test-1.html",
    "example-test-2.html",
    // optionally provide a name and path
    { name: "Example Test 3", path: "example-test-3.html" }
]);

Optionally, give the composed module a name (defaults to "Composition #1"):

QUnit.testSuites( "Example tests", [
    "example-test-1.html",
    "example-test-2.html"
]);

Notes

  • Although it is possible to do so, we do not recommend mixing QUnit Composite suites (QUnit.testSuites) on the same page as regular tests and modules (QUnit.test/test, QUnit.module/module).
  • The QUnit Composite plugin can be used for testing suites on the "file://" protocol unless any of the referenced suites are outside of the test page's directory (e.g. ../otherTest.html) due to web security restrictions. You can work around this restriction by running them in Google Chrome or PhantomJS, with web security disabled — or, of course, by not referencing suites outside of the current test page's directory.