Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I had many failures when I just updated rails (from an edge version a couple of weeks old) to rc1. When I did a full bundle update it picked up the latest rspec-rails (2.13.1 instead of 2.13.0) and everything passed again.

The errors were I think caused by a change in the separation of the tests so database state was leaking between them causing failures but I haven't investigated deeply.

In these sorts of situations I never know whether it is best to 'bundle update' everything and have less information about the source of any problems or just to 'bundle update rails' and not receive the compatibility fixes straight away. How do others do this?

[Edited to add detailed version information and last paragraph].



In rspec-rails' case, that's because an error was caught after the beta1 release, and 2.13.1 introduced the fix.

Generally, I do this:

1) update everything, run `rake rails:update`, and run the tests. Hope this works. If not, figure out if the error is mine or a gem's.

2) If it's a gem's, try to lock it to the exact version I was using and repeat 1).

3) If that doesn't work due to version issues, investigate if the gem has some sort of preview support for rails 4.

4) if not, either send a pull request or an issue.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: