Code Monkey home page Code Monkey logo

nodeunit-httpclient's Introduction

nodeunit-httpclient

HTTP response testing for NodeUnit

Usage

//Setup client with automatic tests on each response
var api = require('nodeunit-httpclient').create({
    port: 3000,
    path: '/api',   //Base URL for requests
    status: 200,    //Test each response is OK (can override later)
    headers: {      //Test that each response must have these headers (can override later)
        'content-type': 'application/json'  )
    }
});

//Automatic tests on response object
exports.test1 = function(test) {
    api.get(test, '/user/nonexistent', {
        status: 404,
        headers: { 'content-type': 'text/plain' },
        body: 'Not found'
    })
};

//Test a response
exports.test2 = function(test) {
    api.get(test, '/user', function(res) {
        //JSON responses are automatically parsed:
        test.equal(res.json, [{ name: 'Eric' }, { 'name': 'Kyle' }]);

        test.done();
    });
};

//POST with data and custom header
exports.test3 = function(test) {
    api.post(test, '/user', {
        headers: { foo: 'bar' },
        data: { name: 'Charlie' } //Objects are serialised as JSON automatically
    }, {
        status: 200
    }, function(res) {
        test.equal(1, 1);
        
        test.done();
    });
};

Changelog

0.2.0

  • Handle 204 No Content responses

nodeunit-httpclient's People

Contributors

elliotttf avatar powmedia avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

nodeunit-httpclient's Issues

Support for HTTPS?

I can't seem to configure the client to be able to make requests to a server that requires HTTPS. Is that supported? If not, what might it take?

Ability to test for 204 status code

When a URL returns HTTP Status 204 (No Content) the httpclient.js breaks because it can't parse the non-existent Content-Type header. This needs fixing.

PATCH support

Please add support for the PATCH verb which should be equal to POST or PUT.

README lists improper variable for where json data is stored.

In your README, you imply that you store json data automatically in res.json:

//Test a response
exports.test2 = function(test) {
api.get(test, '/user', function(res) {
//JSON responses are automatically parsed:
test.equal(res.json, [{ name: 'Eric' }, { 'name': 'Kyle' }]);

    test.done();
});

};

However, you store json data in res.data. Can you update the documentation to reflect this?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.