Em 08-03-2012 05:31, Antonio Tapiador del Dujo escreveu:
On Domingo 04 Marzo 2012 20:36:12 Michael Schuerig escribió:
On Thursday 01 March 2012, Consu wrote:
What will it cost in real money, to upgrade a bigger Rails App?
For the past few weeks I've been working on Rails app that has grown
over about 3 years to around 25kloc. The app was stuck at Rails 2.1.2,
uses quite a few gems/plugins and had a fair number of monkey patches to
Rails itself and the plugins.
It took me 20 to 30 days to convert this app to Rails 3.2.2; the exact
amount of days is hard to pinpoint as I did a lot of other cleanup and
things that weren't strictly necessary, such as rewrite queries in the
new style. Simply put, the effort I spent on this task is utterly
negligible compared to the programming effort in the life of that
application so far. Even more so when the whole project is considered.
What made this update possible at all was the solid test coverage.
I agree with you, Michael. When a developer says "you know things will break,
you just don’t know what, when and how.", it seems to me that there is a lack
of solid test coverage that would show up those failures.
I kind of understand this feeling. I don't write tests for my views, for
example. So, you'd have to manually check all your views to see if some
Rails changes in the view layer broke your application...
I'm curious... How many of you are really testing the output of your
views? I'm not talking about integration tests where you use only a few
parts of the view to test some specific behavior.
Cheers,
Rodrigo.
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
