3 ms·
Upgrading from 4.0 to 4.1 1013 runs, 351 assertions, 6 failures, 832 errors, 0 skips Ouch. Still, it's great to see development on Rails continue. It really
by matthewmacleod 13y ago
Upgrading from 4.0 to 4.1
1013 runs, 351 assertions, 6 failures, 832 errors, 0 skips
Ouch. Still, it's great to see development on Rails continue. It really hits a great sweet spot for small to mid-sized apps.
Edit: Actually easier than I thought; about 10 minutes to figure out the cause and remove a surplus gem, and we're all green. Cool.
- rubiquity 13y agoI think there's some pretty substantial ActiveRecord changes under the hood in Rails 4.1, so likely one of your gems are fighting with it and borking your test suite.
- gargarplex 13y agoWhat is great for large-sized apps?
- matthewmacleod 13y agoInteresting and complex question, that. Larger apps end up being more SOA than monolithic, I suppose. Rails can usually play a part in these, but in my experience it's usually a win to start fragmenting an app into services once it gets beyond a certain size and complexity.