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

v0.2.6

Published

A report for Mocha, creating a HTML file with the test results, based on doc and xunit-file

Downloads

14

Readme

mocha-docfull

A reporter for Mocha, creating a HTML file with the test results, based on doc and xunit-file The HTML files starts with a summary listing the suites tested, with an intern link leading to each suite. Then each suite lists the specs tested, passed or failed, and in case of failure, writes the error in the report.

Installation

npm install mocha-docfull --save

Usage

in config.json, add an environment variable to define the destination path, for the result file: for example

	env{
		"docfull_path":  "C:/results/"
		}

The path has to be absolute.

In the protractor configuration file, add "mocha-docfull" as a reporter:

	framework: 'mocha',
	mochaOpts: {
		reporter: 'mocha-docfull',
		timeout: 5000,
		enableTimeouts: false
		},

You also need to add this in the configuration file:

	onPrepare: function() {
        browser.getCapabilities().then(function (cap) {
            browser.browserName = cap.caps_.browserName;
            browser.browserVersion = cap.caps_.version;
        });
	},

Tests

Contributing

Release History

  • 0.1.0 Initial release
  • 0.2.0 Working version
  • 0.2.1 Fixed the BOM with the CSS, added the browser name and version, and timestamps
  • 0.2.2 Fixed the readme.md
  • 0.2.3 The report now contains the name of the browser and its version
  • 0.2.4 Cleaned the code, added the total number of tests in the summary
  • 0.2.5 Revert to fix a problem with illegal token
  • 0.2.6 Modified the way tests are logged in the console, in case of failure (no more double line)