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

esdoc-test-plugin

v1.0.1

Published

Documentation test plugin for ESDoc

Downloads

3

Readme

ESDoc Documentation Test Plugin

This plugin will convert any Javascript snippet inside descriptions into executable test.

Writing a good documentation often requires to write good examples. Keeping these examples in sync with the actual code is hard when you don't check them. With this plugin, ESDoc will turn any snippet into executable tests and run them each time you build the doc.

Installation

npm install --save esdoc esdoc-test-plugin

Configuration

To enable the plugin, update tour .esdoc.json configuration file:

{
    "source": "./src",
    "destination": "./public",
    "plugin": [
        {
            "name": "./esdoc-test-plugin",
            "option": {
                "path": "./src"
            }
        }
    ]
}

Here is the complete list of configuration options:

| Name | Type | Default | Annotation | Description | |-------------------|-----------|---------|------------|-----------------------------------------------------------------------------------------------------------------| | path | String | | ✓ | The base path to the source directory. Might be the same as the source directive of ESDoc. | | exitOnFailure | Boolean | false | | Should ESDoc exit immediately if a test failed. | | exitWithFailure | Boolean | true | | Should ESDoc exit with an error status if a test failed. | | assert | String | node | ✓ | Which assertion framework to use (one of: chai, chai-expect, chai-assert, expect, expect.js, node). |

Usage

Given you have the following Javascript code and its documentation:

/**
* @param {Number} x
* @param {Number} y
* 
* @return {Number}
*/
const add = (x, y) => x + y;

You can add some test in the description:

/**
 * This function adds two numbers:
 * 
 * ```js
 * const add = require('./add');
 * 
 * assert.equal(add(1, 2), 3);
 * ```
 * 
 * @param {Number} x
 * @param {Number} y
 * 
 * @return {Number}
 */
const add = (x, y) => x + y;

This will generate a single test for the add function.

Note that the require is relative to the plugin.option.path configuration directive (the actual file is located at ./src/add.js).

You can add more test by writing more snippets:

/**
 * This function adds two numbers:
 * 
 * ```js
 * const add = require('./add');
 * 
 * assert.equal(add(1, 2), 3);
 * ```
 *
 * ```js
 * const add = require('./add');
 * 
 * assert.equal(add(-1, -2), -3);
 * ```
 * 
 * @param {Number} x
 * @param {Number} y
 * 
 * @return {Number}
 */
const add = (x, y) => x + y;

You can also use annotation to configure some tests:

/**
 * This function adds two numbers:
 * 
 * ```js#assert=chai
 * const add = require('./add');
 * 
 * add(1, 2).should.equal(3);
 * ```
 * 
 * @param {Number} x
 * @param {Number} y
 * 
 * @return {Number}
 */
const add = (x, y) => x + y;

Annotation are written next to the language with the following format: js[[#name[=value]]...]. If the annotation has no value, its default value will be true.

The path and assert configuration directives can be overridden at the test level using annotations. You can also use the skip annotation to mark a test as skipped.