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

apitest

v0.0.3

Published

apitest =======

Downloads

6

Readme

apitest

A small library to extend supertest's .expect method to fit better with the apisend library.

The main use case is to be able to differentiate between different kinds of errors. For example for authorization, expecting 401 and thinking everything is fine since the tests pass isn't really enough -- a 401 could mean a bunch of different things.

This package should be paired with its cousin package apisend

###Usage:

var apisend = require('apisend'), apitest = require('apitest'), request = require('supertest')
describe('My service', function() {
  var app,
    errors = {
      NO_TOKEN: { code: 1, http: 401, response: 'There is no such access token' },
      LOGIN_FAIL: { code: 2, http: 401, response: 'Login failed' }
    }

  before(function(done) {
    app = require('express')()

    app.use(apisend(errors))
    app.get('/', function(req, res) {
      res.apisend(0)
    })
    app.get('/auth', function(req, res) {
      res.apisend(errors.NO_TOKEN)
    })
    app.listen(3000, done)
  })

  it('should say NO_TOKEN when doing auth', function(done) {
    // request(app).expect(401, done) 
    // ^^ this would work, but lacks precision:
    request(app).get('/auth').api(errors.NO_TOKEN, done)
  })

  it('this test will fail', function(done) {
    // request(app).expect(401, done) 
    // ^^ the above wouldn't throw, but the next one will:
    request(app).get('/auth').api(errors.LOGIN_FAIL, done)
  })

  it('should be able to test for success', function(done) {
    // expect success
    request(app).get('/').api(0, done)
  })

})