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

terst

v0.3.0

Published

A JavaScript testing component with a terse syntax.

Downloads

56

Readme

terst

build status

A JavaScript testing component with a terse syntax. Supported in both Node.js and the browser.

Why?

Take a look at some of the popular JavaScript assertion/testing libraries, most of them are overly verbose.

examples from should.js docs:

var user = {
    name: 'tj'
  , pets: ['tobi', 'loki', 'jane', 'bandit']
};

user.should.have.property('name', 'tj');
user.should.have.property('pets').with.lengthOf(4);

or...

T (user.name)
EQ (user.name, 'tj')
EQ (user.pets.length, 4)

how about from expect.js:

expect(window.r).to.be(undefined);
expect(5).to.be.a('number');
expect([]).to.be.an('array');

or..

T (typeof window.r == 'undefined')
T (typeof 5 == 'number')
T (Array.isArray([]))

Don't even get me started on Node.js assert.

Terst has three main advantages:

  1. There are only six methods to remember. You aren't second guessing what each method really does or constantly referring to the documentation.
  2. Your eyes can quickly scan down the left side of your tests to quickly interpret what each test should do. Terst forces you to be very explicit.
  3. It's very lightweight.

Install

Node.js/Browserify

npm install --save terst

Component

component install jprichardson/terst

Script

<script src="/path/to/terst.js"></script>

Methods

T (value, [msg])

Asserts if the value is truthy.

F (value, [msg])

Asserts if the value is falsey.

EQ (val1, val2, [msg])

Asserts if val1 strictly equals val2.

NEQ (val1, val2, [msg])

Asserts if val does not strictly equal val2.

APPROX (value, expected, delta, [msg])

Asserts if the value is within +- the delta.

THROWS (fun)

Asserts if a function throws i.e. if it does not throw, there is an error.

NOTE: For descriptive errors, you can set terse.autoMsg = true. It's experimental only.

License

(MIT License)

Copyright 2013-2014, JP Richardson [email protected]