search for: mycongress

...a method will be called once with no paramaters, and a second time with a parameter? I''d be tempted to shortcut and just do something like foo.expects(:bar).times(2), but the value used as the parameter when calling it the second time is very important. Thoughts? -Bryan -- http://www.MyCongress.org/ -- coming soon

...is coming from. Logically, it probably is coming from the any_instance magic, but in that case it should be expecting the render_file call. Thoughts? What am I doing wrong in the second case? Is there another way I could mock this? Any help would be greatly appreciated. -Bryan -- http://www.MyCongress.org/ -- coming soon

...ies are judged, and cool prizes are awarded. http://www.railsday2006.com/ Sponsoring Rails Day is a great way to promote your company to the geek demographic. If you''re interested, send an inquiry to sponsor@railsday2006.com and we can work something out. Enjoy. -Bryan -- http://www.MyCongress.org/ -- coming soon

...Is any work being done on organizing Rails Day 2006? As a participant in 2005, it was lots of fun, and I''d really like to see it continued. RailsDay.com seems to be down. Who organized the last one? Will they be running it again? If no one is doing it, I might. -Bryan -- http://www.MyCongress.org/ -- coming soon

...as if each of those expectations is both setup code and a test, and each test relies on all the setup code for the whole test case. Is there anyway to reorganize this code to still be DRY but yet also achieve more granular tests, despite their interdependencies? Thanks, -Bryan -- http://www.MyCongress.org/ -- coming soon

I can understand that it''s easier for rspec to set up a mock in advance of the controller call. But it makes it difficult to do something like: context "The HarkController, given Louie the logged-in user" do setup do post :login, :username => ''louie'', :password => ''atest'' end specify "should redirect Louie to the home