Contents

Feature: route_to matcher

  The `route_to` matcher specifies that a request (verb + uri) is routable.  It
  is most valuable when specifying routes other than standard RESTful routes.

      { :get => "/" }.should route_to(:controller => "welcome")

  Scenario: passing route spec
    Given a file named "spec/routing/widgets_routing_spec.rb" with:
      """
      require "spec_helper"

      describe "routes for Widgets" do
        it "routes /widgets to the widgets controller" do
          { :get => "/widgets" }.
            should route_to(:controller => "widgets", :action => "index")
        end
      end
      """

    When I run "rspec spec/routing/widgets_routing_spec.rb"
    Then the output should contain "1 example, 0 failures"

  Scenario: route spec for a route that doesn't exist (fails)
    Given a file named "spec/routing/widgets_routing_spec.rb" with:
      """
      require "spec_helper"

      describe "routes for Widgets" do
        it "routes /widgets/foo to the /foo action" do
          { :get => "/widgets/foo" }.
            should route_to(:controller => "widgets", :action => "foo")
        end
      end
      """

    When I run "rspec spec/routing/widgets_routing_spec.rb"
    Then the output should contain "1 example, 1 failure"

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
rspec-rails-2.4.1	features/routing_specs/route_to_matcher.feature
rspec-rails-2.4.0	features/routing_specs/route_to_matcher.feature