On 14 Jul 2010, at 18:16, David Kahn wrote:
Excuse to be blunt but I consciously count at least once or more a
day that the discipline of writing tests saves my a$$ --- and that
is conscious, who knows all the other bugs it saves me from. I
encourage you to take the time an discipline to learn this method.
My first large project I did without tests. Tests dont solve
everything but they do mitigate a good portion of the living hell
possible without them. I learned this by experience... hopefully you
will be smarter :)
Practical idea - take two small projects, write one how you would
normally and one strictly following tdd. When you are done judge by:
The results
How you feel about the project and the beauty of your code
How confident you are in making changes to the project
I agree you shouldn't dive into a big project without testing. Small
projects to start off with is the way to go. However, as the original
poster said, he's not even familiar with Rails (and probably Ruby as a
whole). TDD with no prior knowledge of the concept, the language or
the framework you'll be using... bad idea. TDD should be the goal, but
at least get comfortable with the environment imo.
Best regards
Peter De Berdt
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" 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/rubyonrails-talk?hl=en.
