Skip to content
This repository

A quick and easy way to visually test your Rails application's API.

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 app
Octocat-spinner-32 config Added support for missing definitions June 22, 2012
Octocat-spinner-32 lib
Octocat-spinner-32 script Initial commit :) June 20, 2012
Octocat-spinner-32 spec
Octocat-spinner-32 .gitignore Ignore ctags June 22, 2012
Octocat-spinner-32 .rspec Initial commit :) June 20, 2012
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 Gemfile
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile Initial commit :) June 20, 2012
Octocat-spinner-32 api_taster.gemspec
README.md

ApiTaster Build Status Dependency Status

A quick and easy way to visually test out your Rails application's API.

Why?

There are already many awesome API clients (such as Postman), so why reinvent the wheel?

API Taster compared to alternatives, have the following advantages:

  • API endpoints are automatically generated from your Rails routes definition
  • Defining post params is as easy as defining routes
  • Post params can be shared with your test factories

Usage

Add API Taster in your gemfile:

gem 'api_taster', :group => :development

Mount API Taster, this will allow you to visit API Taster from within your app. For example:

Rails.application.routes.draw do
  mount ApiTaster::Engine => "/api_taster" if Rails.env.development?
end

Add API Taster into the autoload paths in development.rb:

config.autoload_paths += %W(
  #{ApiTaster::Engine.root}
)

In routes.rb, define parameters for each API endpoint after the normal routes definition block. For example:

if Rails.env.development?
  ApiTaster.routes do
    get '/users'

    post '/users', {
      :user => {
        :name => 'Fred'
      }
    }

    get '/users/:id', {
      :id => 1
    }

    put '/users/:id', {
      :id => 1, :user => {
        :name => 'Awesome'
      }
    }

    delete '/users/:id', {
      :id => 1
    }
  end
end

Share Params with Test Factories

If you use a test factory such as FactoryGirl, you can require your test factories and share the params. For example in FactoryGirl you can use the attributes_for(:name_of_factory) method.

Missing Route Definitions Detection

Instead of manually finding out which route definitions you need, API Taster provides a warning page that shows you all the missing definitions.

Obsolete / Mismatched Route Definitions Detection

APIs evolve - especially during the development stage. To keep ApiTaster.routes in sync with your route definitions, API Taster provides a warning page that shows you the definitions that are obsolete/mismatched therefore you could correct or remove them.

Use with an Engine

Rails Engines are largely self contained and separated from your main app. Therefore, to use API Taster with an Engine, you would need some extra efforts:

In your app Gemfile, you would also need:

gem "jquery-rails"
gem "bootstrap-sass"

If you are hand-picking Rails components, make sure in your application.rb you have Sprockets enabled:

require "sprockets/railtie"

License

This gem is released under the MIT License.

Author

Fred Wu, originally built for Locomote.

Something went wrong with that request. Please try again.