Order of Tests

Hi Andrew, Thanks for the comment. You are right that most developers do test as they develope, but there is a difference between testing as you go, and TDD :-) I'll have to put "real" TDD on my ever growing list of things to look in to! Cheers, David > David, > > You are welcome, and I fully understand how you are positioned. I am in the > same boat with an older project that I have been working on for the last 12 > months, it isn't that I don't do TDD it is just that this Application is so > huge I am only adopting the TDD for new features. > > BTW, I suggest that along with TDD (Test Driven Development) that one also > look into Agile Methodologies as well. Combined they make for a better, > faster development process. > > BTW if you think about it, most developers use a TDD approach anyway. Just > that it is usually the test that are run last, then fix any problems. So can > be hard to get to switch people around to test first, refactor, test etc. > > > > > Andrew Scott > Senior Coldfusion Developer > Aegeon Pty. Ltd. > www.aegeon.com.au > Phone:+613 8676 4223 > Mobile: 0404 998 273 > > > > hi Andrew, > > Thanks for the input, and as much as I would love to do "real" TDD, > that method of developement isn't used where I work. > > Cheers, > > David > > > > I am going to give some very helpful advice here. > > > > Read up on Test Driven Development, and remember that you are going to > need > > to think differently as well. TDD, which is Test Driven Development is a > way > > to write code in small chunks and get the tests to pass as you develop. > > > > Why is that important, is answered in a book called Test Driven > Development > > by Kent Beck. The idea is that as you develop you are refactoring your > code > > by test development to cover all your code with unit testing. > > > > This form of development is slower, and complex to get your head around if > > you are not used to it. But trust me you'll notice the benefits when it > > comes to maintenance and unforseen problems down the track. > > > > Another thing to remember is something called Mock objects, these can be > > very handy in a situation like you described because you can create a mock > > object and then test for its destruction as what you need to do. Also Mock > > objects are very good for DAO, TAO and such because you are writing tests > > that mimic what they should do and in these cases wouldn't write data back > > to the database if they are mock objects. > > > > Sorry to be a pain and throw this at you, but I think it is important to > > understand Test Driven Development first and how it works to benefit and > > appreciate it. > > > > > > > > > > Andrew Scott > > Senior Coldfusion Developer > > Aegeon Pty. Ltd. > > www.aegeon.com.au > > Phone:+613 8676 4223 > > Mobile: 0404 998 273 > > > > > > > > > > > >