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

scenario-test

v0.1.2

Published

A simple javascript test tool for testing node.js HTTP servers.

Downloads

8

Readme

scenario-test

A simple javascript test tool for testing node.js HTTP servers.

Just write the YAML files!

Install

$ npm install -g scenario-test

Example

First, create a config file,

config.yaml

server: http://localhost:3000
mongodb: mongodb://localhost/test
user: ./user/user.yaml
api:
  - class: user
    path: ./api/user.yaml

scenario: 
  - ./scenario/user.yaml 

then, create your users

./user/user.yaml

- user_id: user1
  with:
    username: user1
    email: [email protected]
    password: user1234

and just describe your APIs,

./api/user.yaml

- API: create
  method: POST
  path: /users
  parameters: 
    username: self.username
    email: self.email
    password: self.password
  response:
    when user sign up ok:
      expect status: 200

- API: login
  method: POST
  path: /login
  parameters:
    username: self.username
    password: self.password
  response:
    when user login ok:
      expect status: 200
      expect header:
        # header to test
      expect body:
        # res.body to test

then, give some scenarios ./scenario/user.yaml

- who: user1 
  what: user.create
  with: 
    path_params:
      # ":id": 42398503298092380
    query_params:
      # "limit": 20
    data_params:
      # "body": {}
  expect: user sign up ok
  obtain:
    # _id: res.body_id

- who: user1
  what: user.login
  expect: user login ok

finally, write a simple js file,

var Scenario = require('./index');
var scenario = new Scenario('./config.yaml');

describe('start test', function() {
  it('should pass all tests', function (done) {
    var options = {
      timeout: 3000
    };

    scenario.start(options, done)
      .then(function(res) {
        // test finish
      })
      .catch(function(error) {
        done(error);
      });
  });
});

and, run your test by typing

$ npm test

the result will look like

API

Test

test a scenario

return a promise

scenario-test.test(scenario)
  .then(function(res){
      // do your stuff
  })
  .catch(function(err){
      // deal with error
  });