openapi-contract-validator v1.0.0

Openapi contract validator

A contract compliance validator for OpenAPI Schemas. Validate a request-response pair against an OpenAPI Schema.

Note: This is not a validator for the OpenAPI Schemas (OAS) themselves. This package uses an OAS to validate a request-response pair against the truth of the OAS.

Note: Not intended or optimized for production environments.

If you're not familiar with Node you're probably not the intended audience for this package. This package contains the validator itself for integration into Javascript-based test frameworks. If you're using a non-js framework you're looking for the language agnostic openapi-contract-validator-server.

Installation

npm install openapi-contract-validator

Supported versions

Usage

TL;DR:

const {Http, Validator} = require('openapi-contract-validator');

const oas = 'path/to/your/openapi-schema.yaml';

const http = new Http();
http.request.baseUrl = 'http://localhost:8080';
http.request.endpoint = '/api/test';
http.request.method = 'GET';

http.response.statusCode = '200';
http.response.headers = {...};
http.response.body = {...};

const validator = new Validator();
const options = {};

validator
    .validate(oas, http, options)
    .then(() => {
        console.log('Validation passed •‿•');
    })
    .catch((error) => {
        console.error('Validation failed (╯°□°)╯︵ ┻━┻');
        throw error;
    });

Importing

First, require the OAS validator itself:

// Require syntax
const {Http, Validator} = require('openapi-contract-validator');

// Import syntax
import {Http, Validator} from 'openapi-contract-validator';

Define a contract

Before we can validate a request-response pair we'll have to define what is correct. This is documented in an OpenAPI Schema.

Provide the OAS in one of the following ways:

1. An absolute path to the OAS file. Valid file extensions are .json, .js, .yaml, and .yml.

   const oas = 'absolute/path/to/your/openapi-schema.yaml';

2. An object of paths to the OAS file with a default. The file under default will always be used.

   const oas = {
       default: 'absolute/path/to/your/openapi-schema.json',
       subSchema: 'absolute/path/to/your/openapi-subschema.yaml',
   };

3. A parsed OAS as an object.

   const oas = {
       openapi: '3.0.2',
       // ...
   };

Detail the HTTP interaction

An HTTP interaction consists of two parts: The request and the response. In order to make oas-validator more library-agnostic I've opted to create an intermediary data structure. Create an instance of Http and add details to it.

const http = new Http();
http.request.baseUrl = 'http://localhost:8080';
http.request.endpoint = '/api/test';
http.request.method = 'GET';

http.response.statusCode = '200';
http.response.headers = {...};
http.response.body = {...};

Validation

The final step is to bring everything together and do the actual validation.

const validator = new Validator();
const options = {};

validator
    .validate(oas, http, options)
    .then(() => {
        console.log('Validation passed •‿•');
    })
    .catch((error) => {
        console.error('Validation failed (╯°□°)╯︵ ┻━┻');
        throw error;
    });

Options

All validator options are optional.

// Full options object with default values
const options = {
    endpoint: http.request.endpoint,
    method: http.request.method,
    statusCode: http.response.statusCode,
    requireAllFields: false,
    concatArrays: false,
    allowEmptyString: false,
};

Contributing

Contributors are always welcome! I really don't care if you are a beginner or an expert, all help is welcome. Help includes code contributions, fixing one of my many typos, helping others, etc.