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

stripe-stateful-mock

v0.0.16

Published

A half-baked, stateful Stripe mock server

Downloads

2,886

Readme

stripe-stateful-mock

Simulates a stateful Stripe server for local unit testing. Makes Stripe calls 50-100x faster than testing against the official server.

Stripe version mocked: 2020-08-27

Supported features:

  • charges: create with the most common test tokens or customer card, retrieve, list, update, capture
  • refunds: create, retrieve, list
  • customers: create, retrieve, update, list, create card, retrieve card, delete card
  • products: create, retrieve, list
  • plans: create, retrieve, list
  • prices: create, retrieve, update, list
  • subscriptions: create, retrieve, list
  • tax plans: create, retrieve, update, list
  • connect accounts: create, delete
  • idempotency

Correctness of this test server is not guaranteed! Set up unit testing to work against either the Stripe server with a test account or this mock server with a flag to switch between them. Test against the official Stripe server occasionally to ensure correctness on the fine details.

Usage

The server can be started in multiple ways but in each case it starts an HTTP server (default port is 8000) which can be connected to with any Stripe client. For example in JavaScript...

const Stripe = require("stripe");
const client = new Stripe("sk_test_foobar", {
    apiVersion: "2020-08-27",
    host: "localhost",
    port: port,
    protocol: "http"
});

The server supports the following settings through environment variables:

  • LOG_LEVEL sets the log output verbosity. Values are: silent, error, warn, info, debug.
  • PORT the port to start the server on. Defaults to 8000.

As a shell command

Install globally: npm i -g stripe-stateful-mock

Run: node stripe-stateful-mock

As part of a Mocha unit test

Install as a development dependency: npm i -D stripe-stateful-mock

In your NPM test script: mocha --require stripe-stateful-mock/autostart

Custom

The server is implemented as an Express 4 application and can be fully controlled. This does not start the server by default.

const http = require("http");
const https = require("https");
const stripeStatefulMock = require("stripe-stateful-mock");

const app = stripeStatefulMock.createExpressApp();
http.createServer(app).listen(80);
https.createServer(options, app).listen(443);

Bonus features

This server supports a few bonus parameters to test scenarios not testable against the real server.

Source token tok_429

Use the charge source token tok_429 to get a 429 (rate limit) response from the server.

Source token tok_500

Use the charge source token tok_500 to get a 500 (server error) response from the server.

Source token tok_forget

Use the charge source token tok_forget to get a normal charge response from the server that is not saved.

Source token chains

Send a source token composed of multiple test tokens separated by pipes (|) to get the response for each call in the order the tokens are composed.

Example 1

tok_chargeDeclinedInsufficientFunds|tok_visa

The first time this charge source token is used an insufficient funds response will be sent. The second time it's used the charge will succeed with a visa transaction.

Example 2

tok_500|tok_500|tok_visa|asdfasdf

The first and second time this charge source token is used a 500 response is returned. The third time the charge will succeed with a visa transaction.

A random string is appended to the end to guarantee this sequence won't be confused for a similar test (eg tok_500|tok_500|tok_visa|hjklhjkl) that may be running simultaneously. It's a lazy hack that accomplishes namespacing.

Existing work

stripe-mock - Stripe's official mock server has better POST body checking but is stateless.

stripe-ruby-mock - Patches the Stripe Ruby client so it only works with Ruby.

mock-stripe - Written in Go and I can't be bothered.