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

bitbox-mock

v1.0.3

Published

A mocking library for BITBOX, used in unit tests for apps that depend on BITBOX.

Downloads

21

Readme

bitbox-mock

Greenkeeper badge

This is a mocking library for BITBOX JavaScript SDK. If you write an app that depends on the BITBOX library, you can use this mocking library to write unit tests.

Unit tests should not call external services. That's the primary difference between unit tests and integration tests. Instead of making live calls with BITBOX, this mocking library can be used instead.

Usage

In a normal app, you would instantiate BITBOX accordingly:

const BITBOXSDK = require('bitbox-sdk')
const BITBOX = new BITBOXSDK()

const result = BITBOX.Address.details(someBCHAddr)

In your unit tests, you can use this mocking library to replace the BITBOX object like so:

const BITBOX = require('bitbox-mock')

const result = BITBOX.Address.details(someBCHAddr)

This mocking library depends on Sinon for mocking. If you want to mock a specific data set, you can override the default return values like this:

const sinon = require('sinon')
const BITBOX = require('bitbox-mock')

// This is an example of your own mocked data.
const myMockData = {
  balance: 0.324,
  cashAddress: 'bchtest:qzsfqeqtdk6plsvglccadkqtf0trf2nyz58090e6tt'
}

BITBOX.Address.details = sinon.stub().returns(myMockData)

const result = BITBOX.Address.details(someBCHAddr)