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

bequiesce

v1.1.28

Published

Because 99.999 Doesn't Just Happen

Downloads

28

Readme

Bequiesce

Because 99.999 doesn't “just happen”

Motivation

Existing tools for testing JavaScript suffer from three problems:

  1. They emphasize DOM testing over module testing.
  2. They are verbose to the point of being hard to maintain.
  3. They mask the true expressiveness of JavaScript.

The Bequiesce test harness begins with a solid basis as a straightforward library regression test tool, while following the guideline that test cases must be easy to read and maintain. Bequiesce does this by using JavaScript's ability to evaluate strings that contain JavaScript code. With this simple approach, the full power of JavaScript remains within the hands of the test developer.

Prerequisites and installation

The Bequiesce utility uses Node.js. Package installation is done via NPM. These are the only two prerequisites.

To install the utility and make it available to your Bash shell, use this command.

[user@host]# npm install -g bequiesce

Usage

The software is invoked from the command line with:

[user@host]# bequiesce [testfile | testdir] 

Pragmas

Bequiesce test packages are composed entirely of JavaScript which are parsed by the test harness. JavaScript statements within a test package are parsed line-by-line and shunted to one of four collections for subsequent evaluation:

  1. common sections
  2. situation sections
  3. propositions
  4. proofs

Test authors develop their test cases in a single source file, organized into groups separated by pragmas. The destination for each parsed line is determined by the presence of these three pragmas: @common, @using, and @testing.

Parsed lines that occur immediately after the common pragma are shunted to the common section: these JavaScript statements become part of the evaluation stream for every test case defined later in the test package.

Parsed lines that occur immediately after a using pragma are shunted to the situation section: these JavaScript statements become part of the evaluation stream for test cases defined within the next testing pragma.

Parsed lines that occur immediately after a testing pragma contain proposition-proof test cases. These lines are split into two halves by the presence of the double-semicolon ( ;; ) signal. Everything to the left of the signal is added to the collection of propositions. Everything to the right of the signal is added to the collection of proofs.

Hello World

Here's what the simplest possible test package might look like.

//@using
var z = x + y;

//@testing
x = 1; y = 2;     ;;     z == 3

License

The Bequiesce command line utility is licensed under the MIT License.

Availability