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

fluid-couchdb-test-harness

v1.1.1

Published

A library to assist in testing CouchDB integration within the Fluid ecosystem.

Downloads

11

Readme

fluid-couchdb-test-harness

This package is intended to test integration with CouchDB. Although it can in theory be used on its own, the harness provided by this package is designed to interact with and tested exclusively with the Fluid IoC Test Framework and the test fixtures provided by this package.

Requirements

The harness provided by this package can be run in one of three modes:

  1. Docker
  2. Vagrant
  3. "External"

Docker

By default, the harness attempts to launch a Docker container with an instance of CouchDB. At time of writing, this is conservatively pinned to CouchDB 2.3.1 (see below for details about CouchDB 3.0).

Vagrant

If you are in an environment (such as Windows 7) where running Docker is not possible, you can set the FLUID_TEST_COUCH_USE_VAGRANT environment variable to use Vagrant instead. See below for details. This will use the same version of CouchDB as the Docker route.

"External"

If you would like to use your own standalone instance of CouchDB, configure it to listen to the same port used by the tests in this package (25984) and set the FLUID_TEST_COUCH_USE_EXTERNAL environment variable. This mode is used by our CI setup, and the tests are run against the latest version of the CouchDB docker container (3.x at time of writing).

Please note, when using an "external" instance, you must ensure that an administrative user named admin exists, whose password is set to admin. In CouchDB 2.x, the default was to use the "admin party", where no username/password is required to access administrative functions. In CouchDB 3.0 and higher, "admin party" has been removed and you must have an administrative username and password set. Thankfully, the process of configuring these at least for docker containers is the same for both CouchDB 2.x and 3.x, i.e. you set two environment variables when creating the container.

You can see examples of these environment variables in the GitHub Actions workflow found in this package's .github folder.

Running the Tests

To run the tests for this package on a local machine, you must have either Docker, Vagrant, or a local instance of CouchDB installed (see above).

Running the Tests Locally

To run tests using docker, use the command npm test. The required Docker containers will be automatically started if they are not already running. To run the tests using Docker or Vagrant, set the relevant environment variable (see above).

More Information

  1. More information about the test fixtures provided by this package.
  2. More information about the harness provided by this package.