Project: RSpec Rails 3.5

Publisher: RSpec

controller spec

Scenarios

simple passing example
controller is exposed to global before hooks
setting a different content type for example json (request type)

Given

a file named "spec/controllers/widgets_controller_spec.rb" with:

require "rails_helper"

RSpec.describe WidgetsController, :type => :controller do
  describe "GET index" do
    it "has a 200 status code" do
      get :index
      expect(response.status).to eq(200)
    end
  end
end

When

I run rspec spec

Then

the example should pass

controller is exposed to global before hooks

Given

a file named "spec/controllers/widgets_controller_spec.rb" with:

require "rails_helper"

RSpec.configure {|c| c.before { expect(controller).not_to be_nil }}

RSpec.describe WidgetsController, :type => :controller do
  describe "GET index" do
    it "doesn't matter" do
    end
  end
end

When

I run rspec spec

Then

the example should pass

setting a different content type for example json (request type)

Given

a file named "spec/controllers/widgets_controller_spec.rb" with:

require "rails_helper"

RSpec.describe WidgetsController, :type => :controller do
  describe "responds to" do
    it "responds to html by default" do
      post :create, { :widget => { :name => "Any Name" } }
      expect(response.content_type).to eq "text/html"
    end

    it "responds to custom formats when provided in the params" do
      post :create, { :widget => { :name => "Any Name" }, :format => :json }
      expect(response.content_type).to eq "application/json"
    end
  end
end

When

I run rspec spec

Then

the example should pass

Last published over 1 year ago by Jon Rowe.

controller spec

RSpec Rails settings