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

wary

v1.1.1

Published

Tiny unit test framework to test code with real files

Downloads

58

Readme

wary

npm version dependencies Build Status Build status

Tiny unit test framework to test code with real files.

Motivation

Running tests that interact with real files has usually been a mess. Tipic solutions include mocking the filesystem module, which can reduce the effectiveness of your test code, or use modules that create a virtual filesystem in RAM.

Wary allows you to easily run test cases on real files, allowing you to increase your trust in the code, by taking the required files as inputs and copying them to a temporal location allowing the test to freely modify them, remove them, etc without harming the original file. The temporal files are later removed for you automatically.

Installation

Install wary by running:

$ npm install --save wary

Documentation

wary.it(name, files, action)

The files declared in the second argument are copied to a temporary location and then automatically removed, so you can freely interact with them within your tests.

Kind: static method of wary
Summary: Declare a unit test
Access: public

| Param | Type | Description | | --- | --- | --- | | name | String | test name | | files | Object | files to use in the test | | action | function | test action |

Example

Promise = require('bluebird')
fs = Promise.promisifyAll(require('fs'))
wary = require('wary')
assert = require('assert')

wary.it 'should write to a file',
	text: 'path/to/text.txt'
, (files) ->
	fs.writeFileAsync(files.text, 'Hello World', encoding: 'utf8').then ->
		fs.readFileAsync(files.text, encoding: 'utf8').then (contents) ->
			assert.equal(contents, 'Hello World')

wary.run() ⇒ Promise

Kind: static method of wary
Summary: Run all tests
Access: public
Example

wary.run()

Support

If you're having any problem, please raise an issue on GitHub and I'll be happy to help.

Tests

Run the test suite by doing:

$ gulp test

Contribute

Before submitting a PR, please make sure that you include tests, and that coffeelint runs without any warning:

$ gulp lint

License

The project is licensed under the MIT license.