Peter De Berdt wrote:
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.
In my experience, this is not necessarily a bad idea. As I said in my
earlier post, I learned test-first development* and Ruby while learning
Rails. I think that, *particularly* when learning a new language and
environment, it is important to set up tests so you know if you're doing
Now, I don't always manage to do this myself, particularly if I'm trying
to closely follow a tutorial (as with my current slow progress through
Real World Haskell). But I think it's worth trying to incorporate tests
as soon as you're off the tutorial and trying to write real code.
Discussion about this a couple months ago made me realize that it would
be interesting to write a basic Ruby (or other) programming text that
taught testing *first*, and then taught the rest of the language syntax
only as a way to implement the tests and make them pass.
* I dislike the term "test-driven development". The tests shouldn't
drive the development; rather, the user's requirements should.
TDD should be the goal, but
at least get comfortable with the environment imo.
Writing tests is a great way to see how the environment behaves...
Peter De Berdt