Re: [rspec-users] Module instance variable remains set

2010-02-22 Thread Harm
Addendum: I'm using rspec 1.3.0, rspec-rails 1.3.2 and ruby 1.9.1p129 On Feb 22, 8:45 pm, Harm wrote: > Hi, > > I have an issue with rSpec when spec'ing a module. The module in > question looks like this: > > module Sheep >   def self.sound >     @sound ||= prod

[rspec-users] Module instance variable remains set

2010-02-22 Thread Harm
. The only way I found to fix it is to manually set the instance variable (with instance_variable_set) to nil. Obviously this is Bad. Is there a way to do this globally or better yet to prevent this? With kind regards, Harm ___ rspec-users mailing list

[rspec-users] Speccing module which should be included in controller

2009-03-18 Thread Harm
never use that fallback only for this particular test. Is there anyway to get rid of this entry in my routes.rb? I tried something like this is a before block: ActionController::Routing::RouteSet.new.add_route("index", :controller => "api_access_control_test", :action =>

[rspec-users] Spec migrations?

2008-04-25 Thread Harm Aarts
restarting transaction: ALTER TABLE `members` DROP `manager` And I do not know if this is the way forward. Does any one have any (relevant) thoughts on this? With kind regards, Harm PS the actual spec: describe Member, "should migrate properly" do it "should migrate correctl

Re: [rspec-users] having trouble specing an ajax request

2008-03-06 Thread Harm Aarts
ere: http://www.rubytutorials.net/2008/02/29/small-rspec-revelations-rjs/ Hope you find it helpful. With kind regards, Harm On 5 mrt 2008, at 15:01, [EMAIL PROTECTED] wrote: > Do I need to spec an AR. If yes, what is the best way to spec this. > here is the code - > > def index > @deals = Deal.p

[rspec-users] attachment_fu with fixtures

2008-01-28 Thread Harm Aarts
fixtures(obviously). More importantly I have no idea where to start... Can someone shed some light on this? With kind regards, Harm ___ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users

[rspec-users] RSpec, RESTful nested routes and :path_prefix

2007-11-07 Thread Harm Aarts
;index', :project_id => , :path_prefix => '/wiki' > response.should be_success >end But that obviously does not work. More importantly I do not believe I should be repeating myself with these path_prefixes. I suspect that RSpec is ignoring the :path_prefix in my

Re: [rspec-users] RSpec, RESTful nested routes and :path_prefix

2007-11-04 Thread Harm Aarts
ld be successful" do get 'index', :project_id => 1 response.should be_success end end Seems OK right? Does RSpec not support nested routes with :path_prefix? Harm > -- > > Message: 11 > Date: Fri, 2 Nov 2007 19:56:22 -0400 > From: "

[rspec-users] RSpec, RESTful nested routes and :path_prefix

2007-11-02 Thread Harm Aarts
Dear list, In the app we are making we have a rout something like this: map.resources :projects do |projects| projects.resources :pages, :controller =>"Wiki::Pages", :path_prefix => "/projects/:project_id/ wiki", :name_prefix => "project_wiki_" end But I can't get RSpec(I'm very new to it)