Rspec testing conditional routing constraints

Question

I'm trying to write some rspec integration tests to test that my conditional routes are routing correctly, but I'm getting a bunch of problems.

In routes.rb:

root :to => "error#ie6", :constraints => {:user_agent => /MSIE 6/}
root :to => "protocol_sets#index", :constraints => UserRoleConstraint.new(/doctor/i)
root :to => "refill_requests#create", :constraints => UserRoleConstraint.new(/member/i)
root :to => "refill_requests#create", :constraints => {:subdomain => "demo"}
root :to => "site#index"

In spec/requests/homepage_routing_spec.rb

require 'spec_helper'

describe "User Visits Homepage" do
  describe "Routings to homepage" do
    it "routes / to site#index when no session information exists" do
      visit root_path      
    end
  end
end

I get the following error when I try to run the test.

Failures:

  1) User Visits Homepage Routings to homepage routes / to site#index when no session information exists
     Failure/Error: visit root_path
     NoMethodError:
       undefined method `match' for nil:NilClass
     # :10:in `synchronize'
     # ./spec/requests/homepage_routings_spec.rb:6:in `block (3 levels) in '

Finished in 0.08088 seconds
1 example, 1 failure

Failed examples:

rspec ./spec/requests/homepage_routings_spec.rb:5 # User Visits Homepage Routings to homepage routes / to site#index when no session information exists

From Googling around I'm guessing there may be a problem with how rspec/capybara handle conditional routes.

Is there anyway to test constraints on routes with rspec and capybara?

Florian · Accepted Answer · 2015-12-18 11:54:41Z

1

As this drove me nuts over the last days, I found the solution with the help of a colleague.

When using named route constraints, like UserRoleConstraint in the example, I resorted to actually stubbing the matches? method of the constraint int he specs that needed it, i.e.:

describe 'routing' do
  context 'w/o route constraint' do 
    before do
      allow(UserRoleConstraint).to receive(:matches?).and_return { false }
    end

    # tests without the route constraint
  end
  context 'w/ route constraint' do 
    before do
      allow(UserRoleConstraint).to receive(:matches?).and_return { true }
    end
  end

  # tests with the route constraint
end

Note that this requires you to have named constraints, which might not apply to your case.

answered Dec 18, 2015 at 11:54

Florian

3,3761 gold badge32 silver badges35 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Hendrik Over a year ago

Thanks for this. Did you find a better solution by now?

Florian Over a year ago

Unfortunately, no.

dkniffin Over a year ago

I think this actually should be allow_any_instance_of(UserRoleConstraint).to receive(:matches?).and_return { true }

Community · Accepted Answer · 2017-05-23 12:25:05Z

0

For the protocol constraint you can just specify an entire url with dummy domain. See this answer.

edited May 23, 2017 at 12:25

CommunityBot

11 silver badge

answered Sep 3, 2012 at 22:48

John Bachir

22.9k30 gold badges162 silver badges238 bronze badges

Collectives™ on Stack Overflow

Rspec testing conditional routing constraints

2 Answers 2

3 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related