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

elastictest

v3.0.0

Published

A simple test harness for elasticsearch functional testing

Downloads

60

Readme

A simple test harness for elasticsearch functional testing

Install

npm install elastictest --save

NPM

Example Script

var suite = new elastictest.Suite();

var doc = {
  index: suite.props.index,
  type: 'mytype',
  id: '1',
  body: {
    foo: 'bar'
  }
};

suite.action( function( done ){
  suite.client.index( doc, done );
});

suite.assert( function( done ){
  suite.client.count({
    index: doc.index,
    type: doc.type
  }, function( err, res ){
    t.equal( res.count, 1, 'record count' );
    done();
  });
});

suite.run();

Usage

Create a new test suite

var suite = new elastictest.Suite();

Perform an 'action' on the database before running assertions

suite.client is an instance of the elasticsearch javascript client, so you can do anything that is supported by that API.

You must call done() when your async operations are complete. You may add as many suite.action sections as you wish per suite.

note the test suite will handle refreshing your index so that the data is up-to-date before the assert operations are run.

suite.action( function( done ){
  suite.client.index( {}, done );
});

Run an 'assert' on the database to test if the actions were successful

suite.assert allows you to run assertion code against the responses from suite.client calls to the database. You can use whatever assertion library you wish as long as it handles the exception catching. In the example below I am using t.equals from npm tape. A full example can be found in ./test.

You must call done() when your async operations are complete. You may add as many suite.assert sections as you wish per suite.

suite.assert( function( done ){
  suite.client.count({
    index: doc.index,
    type: doc.type
  }, function( err, res ){
    t.equal( res.count, 1, 'record count' );
    done();
  });
});

Run the suite

You may provide an optional_callback function to run once the suite is complete. This is useful for alerting your testing framework that work is done for this unit of work.

suite.run( optional_callback );

Use a custom schema when creating your test index

You may provide a schema property when creating your Suite, this will be used whenever creating new indeces.

var suite = new elastictest.Suite( null, { schema: custom_schema });

License

(The MIT License)

Copyright (c) 2013 Peter Johnson <@insertcoffee>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.