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

jupyter-js-auto-test

v1.2.0

Published

Auto scan files under the directory and run test in them

Downloads

3

Readme

Description

This project could scan files under the specific directory and run tests in them. The test report could be print to the terminal or pass to the caller via Callback.

Or you could setup only mode to only run all tests or specific tests a specific file.

How to use it

To run it, you first need to write test.

You could write test by yourself or use the test template and config to setup tests. Either way require the test functions to be exported and having a callback function as their parameter which will callback(testResult[, errorMessage]).

For example (Write by yourself, it also require chalk.)

const chalk = require('chalk')

module.exports = {
    foo
}

function foo(callback) {
    if (1 + 1 === 2) {
        console.log(chalk.green('Test foo passed'))
        callback(true)
    } else {
        console.log(chalk.red('Test foo failed due to '), 'impossible')
        callback(false, 'error message')
    }
}

Or you could use test template and config,

module.exports = {
    foo2,
}

const { TestFunctionConfig, readConfigAndRun } = require('jupyter-js-auto-test')

// in most case, this obj should be the object about to test
const obj = {
    foo2: (callback) => {
        if (1 + 1 === 2) {
            console.log("Object run foo2")
            callback(null)
        } else {
            console.log("Object run foo2")
            callback("impossible")
        }
        
    }
}

function foo2(callback) {
    readConfigAndRun(
        new TestFunctionConfig(obj, 'foo2', [], null),
        callback
    )
}

More Config examples

// having prerunfuncs
new TestFunctionConfig(
            UserLoyaltyLevels,
            'getLevel',
            [level.LevelID],
            null,
            [new TestFunctionConfig(UserLoyaltyLevels, 'addLevel', [level.LevelID, level], null)]
        )

Once you have your test functions, you can run it.

const { setAndRun } = require('jupyter-js-auto-test')
setAndRun('path/to/directory')

If you have any problems or anything to say, please create an issue at github respo, https://github.com/Jupiter0806/JS_Playground/tree/master/my_node_modules/jupyter-js-auto-test I will try to reply as soon as possible.