Handling Design Mistakes in TDD

•

What is DaniWeb IT Discussion Community?

You're currently browsing the Software Developers' Lounge section within the Software Development category of DaniWeb, a massive community of 427,939 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,772 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.

Join our community!

Please support our Software Developers' Lounge advertiser: Programming Forums

Thread Tools Display Modes

Views: 213 | Replies: 2

•

Join Date: Mar 2007

Posts: 9

Reputation: Jusa is an unknown quantity at this point

Rep Power: 0

Solved Threads: 0

Jusa

Offline

Newbie Poster

Handling Design Mistakes in TDD

Jul 18th, 2008

I've thought about getting into test-driven development myself, but one thing I don't quite understand yet is what happens if I make a design mistake, like create a class and later on realize that it should be removed altogether. Removing it would mean all the tests I've written for that class would fail, right? Should I then just remove or modify the tests, too? Somehow it sounds like it shouldn't work this way, but maybe I'm missing something

•

Join Date: Sep 2004

Posts: 6,343

Reputation: Narue has much to be proud of

Rep Power: 29

Solved Threads: 462

Narue

Offline

Expert Meanie

Re: Handling Design Mistakes in TDD

Jul 18th, 2008

>Should I then just remove or modify the tests, too?
That makes sense. You should also modify the tests that rely on that class as well, which (depending on your level of coupling) could mean changes in other classes and other tests.

I'm a programmer. My attitude starts with arrogance, holds steady at condescension, and ends with hostility. Get used to it.