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

chai-changes

v1.3.6

Published

Change assertions for the Chai assertion library

Downloads

26,840

Readme

chai-changes

Build Status NPM Version

chai-changes is an extension to the chai assertion library that provides a set of change-specific assertions.

Assertions

All assertions use a when mechanism.

Using 'expect':

expect(-> codeThatYieldsAChangedResult).to....when ->
  executeTheCodeThatCausesTheChange()

The code within the expect section will be executed first, then the code in the when section will be executed and then the code in the expect section will be executed again and the differences will be asserted.

Same test using 'should':

(-> codeThatYieldsAChangedResult).should....when ->
  executeTheCodeThatCausesTheChange()

when

Executes the build up pre- and post-conditions. First it executes the pre-conditions, then it will execute the provided callback. And after the callback it will assert the post-conditions. It will change the object in the assertion chain to the result of the callback.

Promises

When the callback returns a promise, the post-conditions are executed when the promise is fulfilled.

The when statement will return an assertion promise when the result of the when block is a promise. To use in mocha, you can specify an notify key to trigger done()

expect(-> value).to.change.when(
  -> promise
  notify: done
)

if you use mocha-as-promised, you don't need to specify this notify method

an alternative would be:

expect(-> value).to.change.when(-> promise).then
  -> done()
  (error) -> done(error)

change

Assert if the 'expect/should' changes its outcome when 'when' is executed

result = 0
(-> result).should.change.when -> result += 1
expect(-> result).to.change.when -> result -= 1
expect(-> result).not.to.change.when -> result = result * 1

change.by(delta)

Assert if the change of the 'expect/should' has the provided delta

result = 0
(-> result).should.change.by(3).when -> result += 3
expect(-> result).not.to.change.by(-3).when -> result += 1
expect(-> result).to.change.by(-2).when -> result -= 2

change.from(startValue)

Assert if the change starts from a certain value. The value is compared using a deep equal.

result = ['a', 'b']
(-> result).should.change.from(['a', 'b']).when -> result.push('c')
(-> result).should.change.from(['a', 'b']).to(['a', 'b', 'c']).when -> result.push('c')

change.to(endValue)

Assert if the change ends in a certain value. The value is compared using a deep equal.

result = ['a', 'b']
(-> result).should.change.to(['a', 'b', 'c']).when -> result.push('c')
(-> result).should.change.from(['a', 'b']).to(['a', 'c']).when -> result = ['a', 'c']

increase

Assert if the value increases when an action is performed

result = 0
expect(-> result).to.increase.when -> result += 1
expect(-> result).not.to.increase.when -> result
expect(-> result).not.to.increase.when -> result -= 1

decrease

Assert if the value decreases when an action is performed

result = 0
expect(-> result).to.decrease.when -> result -= 1
expect(-> result).not.to.decrease.when -> result
expect(-> result).not.to.decrease.when -> result += 1

atLeast(amount)

Assert if the value has a minimal change of 'amount'

result = 0
expect(-> result).to.change.by.atLeast(4).when -> result += 5
expect(-> result).to.change.by.atLeast(4).when -> result -= 10

atMost(amount)

Assert if the value has a maximum change of 'amount'

result = 0
expect(-> result).to.change.by.atMost(7).when -> result += 5
expect(-> result).to.change.by.atMost(14).when -> result -= 10

Installation and Setup

Node

Do an npm install chai-changes to get up and running. Then:

var chai = require("chai");
var chaiChanges = require("chai-changes");

chai.use(chaiChanges);

You can of course put this code in a common test fixture file; for an example using Mocha

AMD

Chai Changes supports being used as an AMD module, registering itself anonymously (just like Chai). So, assuming you have configured your loader to map the Chai and Chai Changes files to the respective module IDs "chai" and "chai-changes", you can use them as follows:

define(function (require, exports, module) {
    var chai = require("chai");
    var chaiChanges = require("chai-changes");

    chai.use(chaiChanges);
});

<script> tag

If you include Chai Changes directly with a <script> tag, after the one for Chai itself, then it will automatically plug in to Chai and be ready for use:

<script src="chai.js"></script>
<script src="chai-changes.js"></script>

License

Copyright (c) 2012 Matthijs Groen

MIT License (see the LICENSE file)