On Jan 11, 2008 1:48 PM, David Chelimsky <[EMAIL PROTECTED]> wrote: > On Jan 11, 2008 3:43 PM, Pat Maddox <[EMAIL PROTECTED]> wrote: > > I don't have any problem with that. I do things that way, and I get > > my work done just fine. However, I'm having a tough time clarifying > > my position when talking to people who believe that unit tests should > > not have to change when refactoring either. I don't think they're > > wrong, actually. > > I do. If you read the refactoring book, every refactoring has a "now > change all the clients" step - tests are clients that have to be > changed. It's just part of the deal.
That makes sense. I've never really thought of it that way. > The thing is that, ideally, you don't want to have to make changes to > the tests for object A when you're refactoring B. > > WDYT? Yeah, I buy that. Not everyone does though. Or at least not everyone feels that it's a particularly important goal. Pat _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
