From: Shadowfirebird Date: 2008-08-04T06:22:44+09:00 Subject: Re: unit testing advice Well, I'm not a professional Ruby developer, but I *am* someone that writes code for a living, and I've been an IT contractor. And while I love the idea of TDD, if I were using it professionally then I simply wouldn't be able to afford to be that dogmatic. Even if I always, always, wrote the tests first, sooner or later I would run up against code written by somewhere else who didn't -- and as a contractor, of course, I never got to choose what programming and testing methodologies were being used at all. ("You want me to indent every other line by four tabs? Okay, you're paying.") I'm not criticising anyone for being gung-ho about DTT; I would simply advise everyone to learn how to write tests second, as well. Shadowfirebird. On Sun, Aug 3, 2008 at 9:38 PM, Phlip wrote: > James Britt wrote: > >> That's exactly what is being talked about. >> >> And the issue is that it creates a model file before the developer has >> written a failing test indicating the need for a model file. > > So write the failing test, then run script/generate. Manually writing all > the files that script/generate creates is just heroism. > > > -- Me, I imagine places that I have never seen / The colored lights in fountains, blue and green / And I imagine places that I will never go / Behind these clouds that hang here dark and low But it's there when I'm holding you / There when I'm sleeping too / There when there's nothing left of me / Hanging out behind the burned-out factories / Out of reach but leading me / Into the beautiful sea