|
From: Marcelo de M. S. <cel...@gm...> - 2006-12-19 18:35:09
|
Ah, that's much more clear now, thanks a lot for helping Luke! On 12/19/06, Luke Bayes <lb...@gm...> wrote: > > > Hmmm, I thought this would be the greatest benefit as it would allow me to > > really focus on one thing at a time and then adjust the little > > inconsistencies later - isn't that what test-driven all about? (Design > > first, implement later, in this case implement the server-side later) > > > > Marcelo. > > > Actually - TDD is about combining the design and implementation process > into a series of small steps. It helps us avoid making big design decisions > about how we think an application will work and instead lets us focus in on > implementing the "next most important thing". > > With all that said, of course TDD does help you more cleanly separate the > different layers of an application, and writing tests around a service stub > (or mock) is highly recommended. The only issue I was trying to caution > against is if there were some other developers building the server > concurrently, make sure you're integrating early and often - as these two > layers often get implemented much differently than they're initially > designed. If you're building the sever *after* the client, this would be > much less of a problem. > > > Thanks, > > > Luke > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Asunit-users mailing list > Asu...@li... > https://lists.sourceforge.net/lists/listinfo/asunit-users > > > |