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

test-dome

v0.0.1

Published

Comprehensive environment for isolated high level testing.

Downloads

3

Readme

Installation

To install test dome use command npm install --save-dev test-dome. It is recommended to use TestDome with mocha framework.

Introduction

TestDome is library that currently stubs fs module. It should behave exactly like node.js module, but without operating on actual file system.

Usage

First require("testDome"); module in your test case. In your test step enclose your module under test with testDome.enclose(pathToModule, options);. In mocha framework it will automatically .release system modules, but in other frameworks (like nodeunit) you may do it manually.

Example test file

var testDome = require("test-dome");
var expect = require("chai").expect;

describe("Your code", function() {
    it("should hello world in file at specified path", function() {
        var codeUT = testDome.enclose("./pathToCode", {
            enabled: {
                vfs: true
            }
        });
        codeUT.writeHello("/tmp/helloWorld.txt");
        
        expect(testDome.vfs.getDataOfFile("/tmp/helloWorld.txt", "utf8")).to.equal("Hello World!");
    });
});

Roadmap

Current step

My current target is to mimic whole fs module and test it against external libraries like fs-extra, q, bluebird

Next Steps

  • Allow to use proxyquire and zurvan for checking against time
  • Mimic http module
  • Mimic net module
  • Mimic child_process module
  • Add good mocking solution