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

comest

v0.4.0

Published

Simple command tester

Downloads

12

Readme

comest

Small and lightweight cli-testing framework.

Installation

You can run comest without installing it by using npx:

npx comest

Or you can install it by running:

npm i -g comest

# use it by typing
comest

Usage

Create test files matching *.test.yml like myFile.test.yml in a folder test.

Basic example

This test run the command echo foo and checks 'yo' has been printed on stdout.

name: Simple echo test
command: echo foo
expect:
  status: 0
  stdout: foo

This test run the command echo foo && exit 42 and checks 'yo' has been printed on stdout and return value is 42.

name: Simple echo test
command: echo foo && exit 42
expect:
  status: 42
  stdout: foo

With files

This test will create a tmp file containing "Lorem ipsum" and will replace {file1} with the absolute path of the tmp file ni the command, and execute it. It will then compare the result of the command with the things in expect.

name: Print file content
command: cat {file1}
assets:
  - type: file
    name: file1
    content: Lorem ipsum
expect:
  status: 0
  stdout: Lorem ipsum

This test will fail because the expectation is different

name: Print file content
command: cat {file1}
assets:
  - type: file
    name: file1
    content: Lorem ipsum
expect:
  status: 0
  stdout: dolor sit amet

Multiline

According to the YAML specification, I suggest using |- for multiline (as it keep line break but not the last one).

name: Print my C file content
command: cat {file1}
assets:
  - type: file
    name: file1
    content: |-
        int main () {
            return 56;
        }
expect:
  status: 0
  stdout: |-
      int main () {
          return 56;
      }

Multi steps

name: Steps demo
assets:
  - type: file
    name: file1
steps:
  - command: echo "foo" > {file1}
    expect:
      status: 0
  - command: echo "bar" >> {file1}
  - command: cat {file1}
    expect:
      status: 0
      stdout: |-
        foo
        bar