On Wed, Feb 2, 2011 at 6:24 PM, Trenton Scott wrote:
> >From my Rails project directory in Terminal, I'm able to run 'bundle
> exec rspec spec/' and it works successfully. When I try and run
> 'autotest', however, I get the error(s) below. Note: my .autotest file
> has require 'autotest/growl' and
Hi,
On Sun, Feb 6, 2011 at 05:29, slavix wrote:
> Struggling with nested routing and rspec...
> When I run spec/controllers/admin/website_users_controller_spec.rb
>
> describe Admin::WebsiteUsersController do
> ...
> get :index, :website => @website
Does that need to be:
get :index, :website
I placed a debugger statement in a controller being tested with rspec2
to catch what's going on, but the statement is ignored? Do I have to
do anything special to get the debugger to stop in the controller
under rspec? If I place the debugger statement in the spec, I get a
break -- but I want the b
>From my Rails project directory in Terminal, I'm able to run 'bundle
exec rspec spec/' and it works successfully. When I try and run
'autotest', however, I get the error(s) below. Note: my .autotest file
has require 'autotest/growl' and require 'autotest/fsevent' in it and
I have both installed.
Struggling with nested routing and rspec...
When I run spec/controllers/admin/website_users_controller_spec.rb
describe Admin::WebsiteUsersController do
...
get :index, :website => @website
at this line I get:
ActionController::RoutingError Exception: No route matches
{:website=>#, :controller=>"
Hi all, I'm trying to create a custom matcher that will visit a given
path and check it's authenticated.
Here's what I have so far (using rspec-rails and capybara):
matcher :require_authentication do
match do |path|
visit path
#page.current_path.should == sign_in_path
page.current_pa
