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

cmdt

v1.0.0

Published

Command-line tool for testing command-line tools

Downloads

445

Readme

Build Status Dependencies Status Coverage Status Published Version npm Badge

Cmdt

Cmdt is a command-line tool for testing command-line tools.

This is handy for testing a command line execution result by checking its exit code and output. Commands will be executed in a temporary directory /tmp/cmdt--/ , this directory will be removed after all tests are completed unless -d/--debug flag is specified.

Installation

npm install -g cmdt

Usage

Run tests on specified test files:

cmdt run <file1>.yml <file2>.yml

Run all test files contained in a directory:

cmdt run <dir>

Debug exit code and output of failing tests, temporary directory will be logged and won't be removed at the end of the execution:

cmdt run --debug <file>.yml <dir>

Test File

Set test command, expected exit code and/or output regular expression in a .yml file:

- description: should display user name
  command: whoami
  exitcode: 0
  output: someuser

- command: time
  exitcode: 0
  output: real.+(\r\n?|\n)user.+
  stdout: real.+(\r\n?|\n)user.+

- command: unknowncommand
  exitcode: 1
  stderr: ^some error$

Parameters can also be specified, and used in test command:

- params:
    first_name: 'Theodore'
    last_name: 'Twombly'
    url: 'http://localhost'

- command: 'echo "Hey {first_name} {last_name}!"'
  exitcode: 0
  output: 'echo "Hey Theodore Twombly!"'

- command: 'wget {url}'
  exitcode: 0

Environment variables are available as _env parameter in test commands:

NAME="Theodore Twombly" cmdt run <file>.yml <dir>

- command: 'echo "Hello {_env.NAME}!"'
  exitcode: 0
  output: 'echo "Hello Theodore Twombly!"'

Test fixtures files and directories can be specified in fixtures array, which will then be copied to test execution directory:

# assuming path/to/data_dir/foobar.txt and path/to/another_dir/barfoo.txt exist
- fixtures:
  - path/to/data_dir
  - path/to/another_dir/barfoo.txt

- command: 'file foobar.txt'
  exitcode: 0

- command: 'file barfoo.txt'
  exitcode: 0

Test Fields

Screenshots

Success with directory arg screenshot Failure with file arg on debug mode screenshot

Colophon

Developer's Guide

Build reports: