No commit activity in last 3 years
No release in over 3 years
Helpers for rack-test that mean I don't need to remember the accept header syntax, or whether to prepend HTTP to them.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

>= 0
 Project Readme

Rack::Test::Accepts

Helpers for rack-test that mean I don't need to remember the accept header syntax, or whether to prepend HTTP to them.

Build status

Master branch: Build Status

Why?

Just to make life a bit easier.

Installation

Add this line to your application's Gemfile:

gem 'rack-test-accepts'

And then execute:

$ bundle

Or install it yourself as:

$ gem install rack-test-accepts

Usage

It's easy to add this in where it's needed by including it via the RSpec config:

require 'rack/test/accepts'

RSpec.configure do |config|
  config.include Rack::Test::Accepts, :type => :request

then:

describe "My route", :type => :request do
  let(:body) { { :key => "abcdef" }.to_json }
  before do
    post '/channel/create', body, env(:accepts_json)
  end

It will work for any of the mime types listed in Rack::Mime::MIME_TYPES e.g.

get "/", {}, env(:accepts_zip)
put "/", {}, env(:accepts_xml)
delete "/", {}, env(:accepts_asm)

or whichever crazy format your routes want to accept.

XHR

It also detects XHR in either of two ways.

get "/", {}, env(:accepts_xhr)
get "/", {}, env(:via_xhr)

There's no difference.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request