Could you send us the fixes? Both these issues and the ones for the
events specs are from contributed code, so I'm not as familiar with
them as I am with the stuff I wrote directly.

Michael

On Tue, Apr 14, 2009 at 3:34 AM, DFischer <[email protected]> wrote:
>
> I got rid of all errors except the following:
>
> 1)
> 'PeopleController create email verifications when verifying email
> should not have an auth token' FAILED
> expected: [],
>     got: nil (using ==)
> ./spec/controllers/people_controller_spec.rb:149:
>
> 2)
> 'SessionsController deletes token on logout' FAILED
> expected: [],
>     got: nil (using ==)
> ./spec/controllers/sessions_controller_spec.rb:56:
>
> Finished in 39.214294 seconds
>
>
> Now, essentially... what's the difference between nil and [] in this
> case? The point is deleting the auth token, right? If anyone can
> indulge me on this that would be awesome.
>
> Thanks.
>
> On Apr 14, 2:27 am, DFischer <[email protected]> wrote:
>> Tried to get this running with 2.3.2
>>
>> 1)
>> 'PeopleController create email verifications when verifying email
>> should not have an auth token' FAILED
>> expected: [],
>>      got: nil (using ==)
>> ./spec/controllers/people_controller_spec.rb:149:
>>
>> 2)
>> NoMethodError in 'SessionsController logins and redirects'
>> undefined method `using_open_id?' for #<SessionsController:0x37c3ba4>
>> /Users/Armageddon/Projects/Personal/Sites/LAmatchUP.com/Repository/
>> insoshi/app/controllers/sessions_controller.rb:11:in `create'
>> ./spec/controllers/sessions_controller_spec.rb:16:
>>
>> 3)
>> NoMethodError in 'SessionsController should update person's
>> last_logged_in_at attribute'
>> undefined method `using_open_id?' for #<SessionsController:0x37b2110>
>> /Users/Armageddon/Projects/Personal/Sites/LAmatchUP.com/Repository/
>> insoshi/app/controllers/sessions_controller.rb:11:in `create'
>> ./spec/controllers/sessions_controller_spec.rb:24:
>>
>> 4)
>> NoMethodError in 'SessionsController fails login and does not
>> redirect'
>> undefined method `using_open_id?' for #<SessionsController:0x37a5640>
>> /Users/Armageddon/Projects/Personal/Sites/LAmatchUP.com/Repository/
>> insoshi/app/controllers/sessions_controller.rb:11:in `create'
>> ./spec/controllers/sessions_controller_spec.rb:29:
>>
>> 5)
>> NoMethodError in 'SessionsController remembers me'
>> undefined method `using_open_id?' for #<SessionsController:0x3771bd8>
>> /Users/Armageddon/Projects/Personal/Sites/LAmatchUP.com/Repository/
>> insoshi/app/controllers/sessions_controller.rb:11:in `create'
>> ./spec/controllers/sessions_controller_spec.rb:42:
>>
>> 6)
>> NoMethodError in 'SessionsController does not remember me'
>> undefined method `using_open_id?' for #<SessionsController:0x3760bbc>
>> /Users/Armageddon/Projects/Personal/Sites/LAmatchUP.com/Repository/
>> insoshi/app/controllers/sessions_controller.rb:11:in `create'
>> ./spec/controllers/sessions_controller_spec.rb:48:
>>
>> 7)
>> 'SessionsController deletes token on logout' FAILED
>> expected: [],
>>      got: nil (using ==)
>> ./spec/controllers/sessions_controller_spec.rb:56:
>>
>> 8)
>> NoMethodError in 'SessionsController should redirect deactivated
>> users'
>> undefined method `using_open_id?' for #<SessionsController:0x3a0be84>
>> /Users/Armageddon/Projects/Personal/Sites/LAmatchUP.com/Repository/
>> insoshi/app/controllers/sessions_controller.rb:11:in `create'
>> ./spec/controllers/sessions_controller_spec.rb:83:
>>
>> 9)
>> NoMethodError in 'SessionsController should redirect users with
>> unverified email addresses'
>> undefined method `using_open_id?' for #<SessionsController:0x39ce598>
>> /Users/Armageddon/Projects/Personal/Sites/LAmatchUP.com/Repository/
>> insoshi/app/controllers/sessions_controller.rb:11:in `create'
>> ./spec/controllers/sessions_controller_spec.rb:93:
>>
>> 10)
>> Test::Unit::AssertionFailedError in 'EventsController route generation
>> should map { :controller => 'events', :action => 'show', :id => 1 }
>> to /events/1'
>> The recognized options <{"action"=>"show", "id"=>"1",
>> "controller"=>"events"}> did not match <{"action"=>"show", "id"=>1,
>> "controller"=>"events"}>, difference: <{"id"=>1}>
>> ./spec/controllers/events_routing_spec.rb:15:
>>
>> 11)
>> Test::Unit::AssertionFailedError in 'EventsController route generation
>> should map { :controller => 'events', :action => 'edit', :id => 1 }
>> to /events/1/edit'
>> The recognized options <{"action"=>"edit", "id"=>"1",
>> "controller"=>"events"}> did not match <{"action"=>"edit", "id"=>1,
>> "controller"=>"events"}>, difference: <{"id"=>1}>
>> ./spec/controllers/events_routing_spec.rb:19:
>>
>> 12)
>> Test::Unit::AssertionFailedError in 'EventsController route generation
>> should map { :controller => 'events', :action => 'update', :id => 1}
>> to /events/1'
>> The recognized options <{"action"=>"update", "id"=>"1",
>> "controller"=>"events"}> did not match <{"action"=>"update", "id"=>1,
>> "controller"=>"events"}>, difference: <{"id"=>1}>
>> ./spec/controllers/events_routing_spec.rb:23:
>>
>> 13)
>> Test::Unit::AssertionFailedError in 'EventsController route generation
>> should map { :controller => 'events', :action => 'destroy', :id => 1}
>> to /events/1'
>> The recognized options <{"action"=>"destroy", "id"=>"1",
>> "controller"=>"events"}> did not match <{"action"=>"destroy", "id"=>1,
>> "controller"=>"events"}>, difference: <{"id"=>1}>
>> ./spec/controllers/events_routing_spec.rb:27:
>>
>> Finished in 38.467484 seconds
>>
>> 437 examples, 13 failures
>>
>> Those are the errors. I'm trying to go through them to fix it. However
>> if anyone's already done it, could you post your fixes?
>>
>> Thanks.
> >
>

--~--~---------~--~----~------------~-------~--~----~
Insoshi developer site: http://dogfood.insoshi.com/
Insoshi documentation: http://docs.insoshi.com/

You received this message because you are subscribed to the Google
Groups "Insoshi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/insoshi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to