rspec-rails 2.99.0 → 3.0.0.beta1

data/features/controller_specs/bypass_rescue.feature

@@ -0,0 +1,75 @@
+Feature: bypass rescue
+
+  Use `bypass_rescue` to bypass both Rails' default handling of errors in
+  controller actions, and any custom handling declared with a `rescue_from`
+  statement.
+
+  This lets you specify details of the exception being raised, regardless of
+  how it might be handled upstream.
+
+  Background:
+    Given a file named "spec/controllers/gadgets_controller_spec_context.rb" with:
+      """ruby
+      class AccessDenied < StandardError; end
+
+      class ApplicationController < ActionController::Base
+        rescue_from AccessDenied, :with => :access_denied
+
+        private
+
+        def access_denied
+          redirect_to "/401.html"
+        end
+      end
+      """
+
+  Scenario: standard exception handling using `rescue_from`
+    Given a file named "spec/controllers/gadgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      require 'controllers/gadgets_controller_spec_context'
+
+      describe GadgetsController do
+        before do
+          def controller.index
+            raise AccessDenied
+          end
+        end
+
+        describe "index" do
+          it "redirects to the /401.html page" do
+            get :index
+            expect(response).to redirect_to("/401.html")
+          end
+        end
+      end
+      """
+    When I run `rspec spec/controllers/gadgets_controller_spec.rb`
+    Then the examples should all pass
+
+  Scenario: bypass `rescue_from` handling with `bypass_rescue`
+    Given a file named "spec/controllers/gadgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      require 'controllers/gadgets_controller_spec_context'
+
+      describe GadgetsController do
+        before do
+          def controller.index
+            raise AccessDenied
+          end
+        end
+
+        describe "index" do
+          it "raises AccessDenied" do
+            bypass_rescue
+            expect { get :index }.to raise_error(AccessDenied)
+          end
+        end
+      end
+      """
+    When I run `rspec spec/controllers/gadgets_controller_spec.rb`
+    Then the examples should all pass
+

data/features/controller_specs/controller_spec.feature

@@ -0,0 +1,58 @@
+Feature: controller spec
+
+  Scenario: simple passing example
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe WidgetsController 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
+
+  Scenario: controller is exposed to global before hooks
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      RSpec.configure {|c| c.before { expect(controller).not_to be_nil }}
+
+      describe WidgetsController do
+        describe "GET index" do
+          it "doesn't matter" do
+          end
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the example should pass
+
+  Scenario: controller is extended with a helper module
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      module MyHelper
+        def my_variable
+        end
+      end
+
+      RSpec.configure {|c| c.include MyHelper }
+
+      describe WidgetsController do
+        let(:my_variable) { 'is a value' }
+
+        describe 'something' do
+          specify { expect(my_variable).to eq 'is a value' }
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the example should pass

data/features/controller_specs/engine_routes.feature

@@ -0,0 +1,51 @@
+Feature: engine routes for controllers
+
+  Controller specs can specify the routeset that will be used for the example
+  group. This is most useful when testing Rails engines.
+
+  @unsupported-on-rails-3-0
+  Scenario: specify engine route
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+    """ruby
+    require "spec_helper"
+
+    # A very simple Rails engine
+    module MyEngine
+      class Engine < ::Rails::Engine
+        isolate_namespace MyEngine
+      end
+
+      Engine.routes.draw do
+        resources :widgets, :only => [:show] do
+          get :random, :on => :collection
+        end
+      end
+
+      class WidgetsController < ::ActionController::Base
+        def random
+          @random_widget = Widget.all.shuffle.first
+          redirect_to widget_path(@random_widget)
+        end
+
+        def show
+          @widget = Widget.find(params[:id])
+          render :text => @widget.name
+        end
+      end
+    end
+
+    describe MyEngine::WidgetsController do
+      routes { MyEngine::Engine.routes }
+
+      it "redirects to a random widget" do
+        widget1 = Widget.create!(:name => "Widget 1")
+        widget2 = Widget.create!(:name => "Widget 2")
+
+        get :random
+        expect(response).to be_redirect
+        expect(response).to redirect_to(assigns(:random_widget))
+      end
+    end
+    """
+    When I run `rspec spec`
+    Then the examples should all pass

data/features/controller_specs/isolation_from_views.feature

@@ -0,0 +1,87 @@
+Feature: views are stubbed by default
+
+  By default, controller specs stub views with a template that renders an empty
+  string instead of the views in the app. This allows you specify which view
+  template an action should try to render regardless of whether the template
+  compiles cleanly.
+
+  NOTE: unlike rspec-rails-1.x, the real template must exist.
+
+  Scenario: expect template that is rendered by controller action (passes)
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe WidgetsController do
+        describe "index" do
+          it "renders the index template" do
+            get :index
+            expect(response).to render_template("index")
+            expect(response.body).to eq ""
+          end
+          it "renders the widgets/index template" do
+            get :index
+            expect(response).to render_template("widgets/index")
+            expect(response.body).to eq ""
+          end
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the examples should all pass
+
+  Scenario: expect template that is not rendered by controller action (fails)
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe WidgetsController do
+        describe "index" do
+          it "renders the 'new' template" do
+            get :index
+            expect(response).to render_template("new")
+          end
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the output should contain "1 example, 1 failure"
+
+  Scenario: expect empty templates to render when view path is changed at runtime (passes)
+    Given a file named "spec/controllers/things_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe ThingsController do
+        describe "custom_action" do
+          it "renders an empty custom_action template" do
+            controller.prepend_view_path 'app/views'
+            controller.append_view_path 'app/views'
+            get :custom_action
+            expect(response).to render_template("custom_action")
+            expect(response.body).to eq ""
+          end
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the examples should all pass
+
+  Scenario: expect template to render the real template with render_views when view path is changed at runtime
+    Given a file named "spec/controllers/things_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe ThingsController do
+        render_views
+
+        it "renders the real custom_action template" do
+          controller.prepend_view_path 'app/views'
+          get :custom_action
+          expect(response).to render_template("custom_action")
+          expect(response.body).to match(/template for a custom action/)
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the examples should all pass

data/features/controller_specs/render_views.feature

@@ -0,0 +1,114 @@
+Feature: render_views
+
+  You can tell a controller example group to render views with the
+  `render_views` declaration in any individual group, or globally.
+
+  Scenario: render_views directly in a single group
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe WidgetsController do
+        render_views
+
+        describe "GET index" do
+          it "says 'Listing widgets'" do
+            get :index
+            expect(response.body).to match /Listing widgets/m
+          end
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the examples should all pass
+
+  Scenario: render_views on and off in nested groups
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe WidgetsController do
+        context "with render_views" do
+          render_views
+
+          describe "GET index" do
+            it "renders the actual template" do
+              get :index
+              expect(response.body).to match /Listing widgets/m
+            end
+          end
+
+          context "with render_views(false) nested in a group with render_views" do
+            render_views false
+
+            describe "GET index" do
+              it "renders the RSpec generated template" do
+                get :index
+                expect(response.body).to eq("")
+              end
+            end
+          end
+        end
+
+        context "without render_views" do
+          describe "GET index" do
+            it "renders the RSpec generated template" do
+              get :index
+              expect(response.body).to eq("")
+            end
+          end
+        end
+
+        context "with render_views again" do
+          render_views
+
+          describe "GET index" do
+            it "renders the actual template" do
+              get :index
+              expect(response.body).to match /Listing widgets/m
+            end
+          end
+        end
+      end
+      """
+    When I run `rspec spec --order default --format documentation`
+    Then the output should contain:
+      """ruby
+      WidgetsController
+        with render_views
+          GET index
+            renders the actual template
+          with render_views(false) nested in a group with render_views
+            GET index
+              renders the RSpec generated template
+        without render_views
+          GET index
+            renders the RSpec generated template
+        with render_views again
+          GET index
+            renders the actual template
+      """
+
+  Scenario: render_views globally
+    Given a file named "spec/support/render_views.rb" with:
+      """ruby
+      RSpec.configure do |config|
+        config.render_views
+      end
+      """
+    And a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe WidgetsController do
+        describe "GET index" do
+          it "renders the index template" do
+            get :index
+            expect(response.body).to match /Listing widgets/m
+          end
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the examples should all pass
+    

data/features/directory_structure.feature

@@ -0,0 +1,71 @@
+Feature: Directory Structure
+
+  Specs are usually placed in a canonical directory structure that describes
+  their purpose.
+
+  * Model specs reside in the `spec/models` directory
+  * Controller specs reside in the `spec/controllers` directory
+  * Request specs reside in the `spec/requests` directory
+  * Feature specs reside in the `spec/features` directory
+  * View specs reside in the `spec/views` directory
+  * Helper specs reside in the `spec/helpers` directory
+  * Mailer specs reside in the `spec/mailers` directory
+  * Routing specs reside in the `spec/routing` directory
+
+  If you follow this directory structure, RSpec will automatically include the
+  correct test support functions for each type of test.
+
+  Application developers are free to use a different directory structure, but
+  will need to specify the types manually by adding a `:type` metadata key (for
+  example, `describe WidgetsController, :type => :controller`)
+
+  Scenario: Specs in the `spec/controllers` directory automatically tagged as controller specs
+    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe WidgetsController do
+        it "responds successfully" do
+          get :index
+          expect(response.status).to eq(200)
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the example should pass
+
+  Scenario: Specs in other directories must have their types specified manually
+    Given a file named "spec/functional/widgets_controller_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe WidgetsController, :type => :controller do
+        it "responds successfully" do
+          get :index
+          expect(response.status).to eq(200)
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the example should pass
+
+  Scenario: Specs in canonical directories can override their types
+    Given a file named "spec/routing/duckduck_routing_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      Rails.application.routes.draw do
+        get "/example" => redirect("http://example.com")
+      end
+
+      # Due to limitations in the Rails routing test framework, routes that
+      # perform redirects must actually be tested via request specs
+      describe "/example", :type => :request do
+        it "redirects to example.com" do
+          get "/example"
+          expect(response).to redirect_to("http://example.com")
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the example should pass