talkrz/rest-spec

A small library for describing and testing REST APIs in PHP

, _(*1)

rest-spec

A simple library for creating self-verifying API specifications, and end-to-end testing written in PHP., _(*2)

I do not recommend to use in on production yet, however will be happy if you will., _(*3)

Installation

You can install rest-spec by Composer., _(*4)

Add package to your project's composer.json file:, _(*5)

{
    "require-dev": {
        "talkrz/rest-spec": "dev-master"
    }
}

Install it with Composer:, _(*6)

composer install

Usage

Basic example: describing GitHub API

Create rest-spec directory in your project's root., _(*7)

Create github.php file (you can choose any file name) inside it with an API specification:, _(*8)

<?php
# rest-spec/github.php

api('https://api.github.com', function() {
    url('/repos/{userName}/{repoName}', 'Fetch user repository data', function() {
        useCase('Fetch octocat\'s hello-world repository', function() {
            givenRequest()
                ->method('GET')
                ->headers([
                    'User-agent' => 'rest-spec'
                ]);

            expectResponse()
                ->toHaveStatusCode(200)
                ->toHaveHeaders([
                    'Content-Type' => 'application/json; charset=utf-8',
                    'Cache-Control' => 'public, max-age=60, s-maxage=60',
                    'Access-Control-Allow-Origin' => '*',
                ])
                ->toBeJson()
                ;
        })->withExampleParameters([
            'userName' => 'octocat',
            'repoName' => 'hello-world',
        ]);
    });
});

Run rest-spec, _(*9)

php vendor/bin/rest-spec

That's it!, _(*10)

As a result of this command you should see result of verifying previously defined specification against real API:, _(*11)

, _(*12)

Always up-to-date specification

This library has two main puproses. First one is to provide API specification that is always up-to-date., _(*13)

Let's change response specification in previous example to one that is not valid:, _(*14)

<?php
# rest-spec/github.php

api('https://api.github.com', function() {
    url('/repos/{userName}/{repoName}', 'Fetch user repository data', function() {
        useCase('Fetch octocat\'s hello-world repository', function() {

        // ...
                ->toHaveHeaders([
                    'Content-Type' => 'application/json', // wrong header!
                    'Cache-Control' => 'public, max-age=60, s-maxage=60',
                    'Access-Control-Allow-Origin' => '*',
                ]);
        // ...
    });
});

After running rest-spec we see, that actual response contains different header than in specification, so we know that we need to update it:, _(*15)

, _(*16)

The other purpose is testing of your application. As rest-spec perform calls to actual application, it can detect problems. Of course you should remember that such end-to-end testing is very limited. It tests only very narrow set of features and paths of code execution inside application. Well written set of unit tests is far more important for detecting bugs., _(*17)