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-context

v1.3.0

Published

context loader for unit tests

Downloads

13

Readme

Context Loader

Used for loading unit tests in a given file context.

This allows running tests within another files context. The result is as if your unit tests were written at the bottom of that the specified file. Files are pre-compiled (see 'supported formats');

For examples, see the /tests directory.

But globals are bad, right? Why make this? I need this functionality for a project.

Supported formats

  • ES5
  • ES6 (Babel)
  • JSX
  • Typescript

Examples (using Mocha & Chai)

ES5

/file.js

function addOne(x) {
  return x + 1;
}

/test.js

var expect = require('chai').expect;
// load 'test-context' module
var context = require('test-context');
// pass in a relative path
context('./file.js');

describe('addOne', function() {
  it('increments the input', function() {
    expect(addOne(1)).to.equal(2);
  });
});
ES6 (ES2015)

/file.js

const addOne = (x) => x + 1;

/test.js

var expect = require('chai').expect;
var context = require('test-context');
// ES6 requires an additional parameter { babel: true }
// pass in Babel options by adding { babelOptions: { ... } }
// or create a .babelrc file
context('./file.js', { babel: true });

describe('addOne', function() {
  it('increments the input', function() {
    expect(addOne(1)).to.equal(2);
  });
});
Typescript

/file.ts

const addOne = (x: number): number => x + 1;

/test.js

var expect = require('chai').expect;
var context = require('test-context');
// pass in ts options by adding { tsOptions: { ... } }
// or create a tsconfig.json file
context('./file.ts');

describe('addOne', function() {
  it('increments the input', function() {
    expect(addOne(1)).to.equal(2);
  });
});