Specs epic fail under Rails rc5 #654

Closed
justinfrench opened this Issue Aug 15, 2011 · 4 comments

Comments

Projects
None yet
2 participants
@justinfrench
Owner

justinfrench commented Aug 15, 2011

Almost every test fails with wrong number of arguments (1 for 0), but we seem to be swallowing exactly where in the stack the error is really happening. Haven't yet tried it with a real app to know if it's just spec related or not. Same specs pass under rc4.

@twalpole

This comment has been minimized.

Show comment
Hide comment
@twalpole

twalpole Aug 15, 2011

Collaborator

This is because posts_path now called with a parameter :format=>nil and in spec_helper.rb posts_path doesnt accept any parameters

Collaborator

twalpole commented Aug 15, 2011

This is because posts_path now called with a parameter :format=>nil and in spec_helper.rb posts_path doesnt accept any parameters

@justinfrench

This comment has been minimized.

Show comment
Hide comment
@justinfrench

justinfrench Aug 15, 2011

Owner

@twalpole Awesome. Any ideas why the specs kind of swallowed the stack trace / ability to find where this came from?

Owner

justinfrench commented Aug 15, 2011

@twalpole Awesome. Any ideas why the specs kind of swallowed the stack trace / ability to find where this came from?

@justinfrench

This comment has been minimized.

Show comment
Hide comment
@justinfrench

justinfrench Aug 15, 2011

Owner

Running tests now... much greener!

Owner

justinfrench commented Aug 15, 2011

Running tests now... much greener!

@twalpole

This comment has been minimized.

Show comment
Hide comment
@twalpole

twalpole Aug 15, 2011

Collaborator

Not sure why its swallowing the real location of the error, I think it loses it somewhere in rspec - the change in rails that changed the behavior is rails/rails@036f775

Collaborator

twalpole commented Aug 15, 2011

Not sure why its swallowing the real location of the error, I think it loses it somewhere in rspec - the change in rails that changed the behavior is rails/rails@036f775

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment