Comments on: Why write the unit tests first? http://www.richardlord.net/blog/why-write-the-unittest-first Actionscript/Flex, PHP and Java developer Sat, 24 Jul 2010 00:46:07 +0000 hourly 1 http://wordpress.org/?v=3.0 By: gropapa http://www.richardlord.net/blog/why-write-the-unittest-first/comment-page-1#comment-33767 gropapa Sat, 06 Feb 2010 15:02:15 +0000 http://www.richardlord.net/?p=434#comment-33767 we can consider the test cases are the "call for the code of " different use case thought during the uml analysis don't we? we can consider the test cases are the “call for the code of ” different use case thought during the uml analysis don’t we?

]]> By: Torbjørn Caspersen http://www.richardlord.net/blog/why-write-the-unittest-first/comment-page-1#comment-33739 Torbjørn Caspersen Fri, 05 Feb 2010 13:52:35 +0000 http://www.richardlord.net/?p=434#comment-33739 @Richard Thanks for the clarification, that makes a lot more sense. BTW. Saw your MVC presentation at Flash on the beach last year. Liked it a lot. @Richard Thanks for the clarification, that makes a lot more sense.

BTW. Saw your MVC presentation at Flash on the beach last year. Liked it a lot.

]]> By: Richard http://www.richardlord.net/blog/why-write-the-unittest-first/comment-page-1#comment-33737 Richard Fri, 05 Feb 2010 12:51:17 +0000 http://www.richardlord.net/?p=434#comment-33737 @Torbjørn No, in this context interface = the methods and properties a class exposes for other code to interact with it. I just posted another item elaborating on this - <a href="/blog/test-the-interface-not-the-implementation" rel="nofollow">Test the interface, not the implementation</a> @Ben Yes, the first time you do it TDD seems to take a lot of extra time, but once you get good at it the increased development time is minimal, and the overall reduction in bugs means greater productivity overall. @Torbjørn No, in this context interface = the methods and properties a class exposes for other code to interact with it. I just posted another item elaborating on this – Test the interface, not the implementation

@Ben Yes, the first time you do it TDD seems to take a lot of extra time, but once you get good at it the increased development time is minimal, and the overall reduction in bugs means greater productivity overall.

]]> By: Ben Beaumont http://www.richardlord.net/blog/why-write-the-unittest-first/comment-page-1#comment-33734 Ben Beaumont Fri, 05 Feb 2010 12:26:30 +0000 http://www.richardlord.net/?p=434#comment-33734 Agree whole-heartedly. I'm the only Flash developer in the company I work for, and I started using TDD ideas in the last few projects I've worked on. I've found it really is useful and changes the way I think about coding for the better. It's initially a bit had to see the benefits, as it requires time writing tests which are non-production code, but once you commit to it, the time to develop the production code can be decreased quite dramatically. It's also very useful for regressive testing to check everything is in order prior to commiting it. Agree whole-heartedly. I’m the only Flash developer in the company I work for, and I started using TDD ideas in the last few projects I’ve worked on. I’ve found it really is useful and changes the way I think about coding for the better.
It’s initially a bit had to see the benefits, as it requires time writing tests which are non-production code, but once you commit to it, the time to develop the production code can be decreased quite dramatically.
It’s also very useful for regressive testing to check everything is in order prior to commiting it.

]]> By: Torbjørn Caspersen http://www.richardlord.net/blog/why-write-the-unittest-first/comment-page-1#comment-33733 Torbjørn Caspersen Fri, 05 Feb 2010 12:21:31 +0000 http://www.richardlord.net/?p=434#comment-33733 Interesting, test driven development is one of the many thing I've wanted to get into, but haven't got around to. One thing that puzzles me: 3. Test the interface. Does that mean that all classes that are to be tested must implement an interface? Seems like a lot of overhead. Interesting, test driven development is one of the many thing I’ve wanted to get into, but haven’t got around to.

One thing that puzzles me: 3. Test the interface. Does that mean that all classes that are to be tested must implement an interface? Seems like a lot of overhead.

]]>