Abao

RAML testing tool

Abao is a command-line tool for testing API documentation written in RAML format against its backend implementation. With Abao you can easily plug your API documentation into the Continous Integration system like Travis CI or Jenkins and have API documentation up-to-date, all the time. Abao uses the Mocha for judging if a particular API response is valid or if is not.

Features

• Verify that each endpoint defined in RAML exists in service
• Verify that each endpoint url params defined in RAML are supported in service
• Verify that each endpoint request HTTP headers defined in RAML are supported in service
• Verify that each endpoint request body defined in RAML is supported in service - verify by validating the JSON schema
• Verify that each endpoint response HTTP headers defined in RAML are supported in service
• Verify that each endpoint response body defined in RAML is supported in service - verify by validating the JSON schema

Installation

Install stable version

npm install -g abao

Install latest developement version in GitHub branch

npm install -g git://github.com/cybertk/abao.git#master

Get Started Testing Your API

abao api.raml http://api.example.com

Writing testable RAML

Abao validates the response from server against jsonschema defines in RAML, so there must be schema section in defined in RAML.

Hooks

Abao can be configured to use hookfiles to do basic setup/teardown between each validation (specified with the --hookfiles flag). Hookfiles can be in javascript or coffeescript, and must import the hook methods.

NOTE: The hookfile's extension must be .coffee if it's written in coffeescript.

Requests are identified by their name, which is derived from the structure of the RAML. You can print a list of the generated names with --names.

Example

Get Names:

$ abao single-get.raml --names
GET /machines -> 200

Write a hookfile in JavaScript:

var hooks = require('hooks');

hooks.before('GET /machines -> 200', function(test, done) {
    test.request.query = {color: 'red'};
    done();
});

hooks.after('GET /machines -> 200', function(test, done) {
    machine = test.response.body[0];
    console.log(machine.name);
    done();
});

hooks.before('GET /machines -> 200 second test case', function(test, done) {
    test.request.query = {color: 'red'};
    done();
});

hooks.after('GET /machines -> 200 second test case', function(test, done) {
    machine = test.response.body[0];
    console.log(machine.name);
    done();
});

Write a hookfile in CoffeeScript:

{before, after} = require 'hooks'

before 'GET /machines -> 200', (test, done) ->
  test.request.query =
    color: 'red'
  done()

after 'GET /machines -> 200', (test, done) ->
  machine = test.response.body[0]
  console.log machine.name
  done()

Run validation:

$ abao single-get.raml http://api.example.com --hookfiles=*_hooks.*

Abao also supports callbacks before and after all tests:

{beforeAll, afterAll} = require 'hooks'

beforeAll (done) ->
  # do setup
  done()

afterAll (done) ->
  # do teardown
  done()

If beforeAll, afterAll, before and after are called multiple times, the callbacks are executed serially in the order they were called.

test.request

• server - Server address, provided from CLI.
• path - API endpoint path, parsed from RAML.
• method - http method, parsed from RAML.
• params - URI parameters, parsed from RAML uriParameters section, default to {}.
• query - object containing querystring values to be appended to the path, default to {}.
• headers - http headers, parsed from RAML headers section, default to {}.
• body - entity body for PATCH, POST and PUT requests. Must be a JSON-serializable object. Parsed from RAML example section, default to {}

test.response

• status - Expected http response code, parsed from RAML.
• schema - Expected schema of http response, parsed from RAML schema section.
• headers - Headers object got from testing server, default to {}
• body - http json body got from testing server. default to null

Command Line Options

Usage:
  abao <path to raml> <api_endpoint> [OPTIONS]

Example:
  abao ./api.raml http://api.example.com

Options:
  --hookfiles, -f   Specifes a pattern to match files with before/after hooks
                    for running tests                            [default: null]
  --names, -n       Only list names of requests (for use in a hookfile). No
                    requests are made.                          [default: false]
  --reporter, -r    Specify the reporter to use                [default: "spec"]
  --header, -h      Extra header to include in every request. The header must
                    be in KEY:VALUE format, e.g. '-h Accept:application/json'.
                    This option can be used multiple times to add multiple
                    headers
  --hooks-only, -H  Run test only if defined either before or after hooks
  --grep, -g        only run tests matching <pattern>
  --invert, -i      inverts --grep matches
  --timeout, -t     set test-case timeout in milliseconds        [default: 2000]
  --reporters       Display available reporters
  --help            Show usage information
  --version         Show version number

Run Tests

$ npm test

Contribution

Any contribution is more than welcome!