That’s normal. Remember that params exists because there is an http
request issued. In your spec, you don’t tell Rspec anything about any
request. So you could create a mock for params. If I recall correctly
you would have to do something like this:
describe ApplicationHelper do
it “should be active if controller is same” do
controller.params = {:controller => ‘whatever_value’}
tab_class(‘royalty_statement’).should include(‘active’)
end
end
That’s normal. Remember that params exists because there is an http
request issued. In your spec, you don’t tell Rspec anything about any
request. So you could create a mock for params. If I recall correctly
you would have to do something like this:
Thanx fernando
i try the following
it “should be active if controller is same” do
params = {:controller => ‘royalty_statement’}
tab_class(‘royalty_statement’).should include(‘active’)
end
but it doesn’t work out. it gives me same error as previus.
it “should be active if controller is same” do
params = {:controller => ‘royalty_statement’}
tab_class(‘royalty_statement’).should include(‘active’)
end
but it doesn’t work out. it gives me same error as previous.
Nah it doesn’t work that way, because remember that RSpec is just Ruby
code. ‘it’ is just a method, “should be active …” is just an argument,
and then you specify a block of code.
So when you define params = …, you are actually defining a local
variable, but that variable is not available inside the controller when
the spec is run. That’s why I find controllers so painful to spec. I
prefer to use cucumber and webrat for that purpose.
Anyway, I thought that setting controller.params would do the trick but
no.
Maybe you’ll have to force a get request then? so it would be:
get :action_name
We need to wait for rspec-rails experts advice.
By the way the same problem applies to session, so you might be luckier
looking for info about simulating session in rspec and then apply the
same technique to params.