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

rest-bdd-testing

v0.6.0

Published

Toolchain for testing REST API, in BDD style.

Downloads

28

Readme

rest-bdd-testing

Toolchain for testing REST API, in BDD style.

npm Build Status Coverage Status

Installation

rest-bdd-testing is available on npm. To install it, type:

$ npm install rest-bdd-testing

Usage

Here is sample usage of this package with mocha.

const http = require('http');
const URL = require('url');
const assert = require('assert');

import {Given, Update} from 'rest-bdd-testing';

describe('Simple usage of REST BDD Tesing in mocha', function() {
    let app, given;

    before(function(done) {
        app = http.createServer((req, res) => {
            let parsedUrl = URL.parse(req.url,true);

            if (parsedUrl.pathname.endsWith('null')) {
                res.writeHead(404, {'Content-Type': 'text/plain'});
                res.end('404 Not found');
            } else {
                res.setHeader('Content-Type', 'application/json;charset=utf-8');
                res.end(JSON.stringify({
                    foo: 'bar'
                }));
            }

        }).listen(done);
    });

    after(function(done) {
        given.end();
        app.close(done);
    });

    it('Happy Scenario', async function() {
        given = new Given(app, 'Happy Scenario', 'When name is  provided, result should be caught.', {
            autodump: './given.json',
            autodoc: './given.md',
            url: '/books/id: 1/writers/name:john?fields=[fullName,age]&sort=-id',
            verb: 'GET',
        });

        let fulfilledRequest = await given.requestBaseCall();
        assert.deepStrictEqual(fulfilledRequest.response.status, 200);
    });

    it('Unhappy Scenario', async function() {
        let newFulfilledRequest = await given.when('Name is null', 'The name url parameter is null', {
            urlParams: new Update({'name': null})
        });

        assert.deepStrictEqual(newFulfilledRequest.response.status, 404);
    });

});

If autodump or autodoc presents, the given.end() creates 2 files for dumping and documenting given(story);

Dumping Story

The json file for above story:

{
    "baseCall": {
        "title": "Happy Scenario",
        "description": "When name is  provided, result should be caught.",
        "url": "/books/:id/writers/:name",
        "verb": "GET",
        "query": {
            "fields": "[fullName,age]",
            "sort": "-id"
        },
        "urlParams": {
            "id": "1",
            "name": "john"
        },
        "response": {
            "status": 200,
            "headers": {
                "content-type": "application/json;charset=utf-8",
                "date": "Thu, 18 Apr 2019 21:25:41 GMT",
                "connection": "close",
                "content-length": "13"
            },
            "json": {
                "foo": "bar"
            }
        }
    },
    "calls": [
        {
            "title": "Name is null",
            "urlParams": {
                "id": "1",
                "name": null
            },
            "description": "The name url parameter is null",
            "response": {
                "status": 404,
                "headers": {
                    "content-type": "text/plain",
                    "date": "Thu, 18 Apr 2019 21:25:41 GMT",
                    "connection": "close",
                    "transfer-encoding": "chunked"
                },
                "body": "404 Not found"
            }
        }
    ]
}

Documenting Story

The md file for above story:

## Happy Scenario

### GET /books/:id/writers/:name

When name is  provided, result should be caught.

### Url Parameters

Name | Example
---|---
id | 1
name | john

### Query Strings

Name | Example
---|---
fields | [fullName,age]
sort | -id

### Response: 200

#### Headers

* date: Thu, 18 Apr 2019 21:55:43 GMT
* connection: close
* content-length: 13

#### Body:

Content-Type: application/json

```json
{
    "foo": "bar"
}
```

---

## WHEN: Name is null

### GET /books/:id/writers/:name

The name url parameter is null

### Url Parameters

Name | Example
---|---
id | 1
name | 

### Response: 404

#### Headers

* date: Thu, 18 Apr 2019 21:55:43 GMT
* connection: close
* transfer-encoding: chunked

#### Body:

Content-Type: text/plain

```
404 Not found
```