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 🙏

© 2025 – Pkg Stats / Ryan Hefner

crosstest

v2.1.1

Published

Test command line

Readme

Crosstest

Crosstest is test command line uses to link and run test in each project with same command and style. It's also provide code pattern for javascript project.

Requirement

  • To use with node.js and javascript in browser. It requires customize test_it version.
  • To use with iOS/Mac OS project. It requires GHUnit.

Other framework will add in future.

Installation

npm install crosstest

How to run test

  • Node.js

Test file have to export test variable to make it runnable with Crosstest.

export.test = {
  'before all': function (test) {
    // This method will run before all method. 
  },
  
  'before each': function (test) {
    // This method will run before invoke each test. (setup)
  },
  
  'test name': function (test) {
    // Test method
  },
  
  'after each': function (test) {
    // This method will run after each test. (teardown)
  },
  
  'after all': function (test) {
    // This method will run after all method. 
  }
}

After create test file use ct command run it.

ct file.js

It can run all test file with ct <directory name> but file must have Test in front of it name e.g. TestLogin.js

  • GHUnit

Create GHUnit target and make it runnable in command line with this guide. And use ct run it like below

ct <project folder> <target> <class name>/<method name>

Class name and method name is optional. If it's not specify, Crosstest will run every class and every method.

  • Suite

Crosstest also have suite file which can tell which test file need to run in group. It's json file and have format like below.

{
  "name": "Suite name",
  "verbose": false,
  "script": "Script.js",
  "suite": [
    {
      "file": "<directory or file name>",
      "name": "Test name",
      "verbose": false
    }
  ]
}

script property use to point to script file that define before and after execution this suite. It's javascript file and have pattern like below.

exports.scripts = {
  before: {
    each: function (callback) {
      // Run this before each file.
      callback()
    },
    all: function (callback) {
      // Run this before every file.
      callback()
    }
  },
  after: {
    each: function (callback) {
      // Run this after each file.
      callback()
    },
    after: function (callback) {
      // Run this after every file.
      callback()
    }
  }
}