<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Unit testing session</title><link>http://blogs.msdn.com/josealmeida/archive/2004/07/05/173147.aspx</link><description>During TechEd'04 in Amsterdam I attended a Birds Of a Feather session on how to integrate unit testing into the Software Development Life-Cycle. For those who are unfamiliar with the format of these sessions, it's a speaker moderated discussion, where</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Unit testing session</title><link>http://blogs.msdn.com/josealmeida/archive/2004/07/05/173147.aspx#173188</link><pubDate>Mon, 05 Jul 2004 20:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:173188</guid><dc:creator>SBC</dc:creator><description>good posting.</description></item><item><title>re: Unit testing session</title><link>http://blogs.msdn.com/josealmeida/archive/2004/07/05/173147.aspx#173414</link><pubDate>Tue, 06 Jul 2004 04:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:173414</guid><dc:creator>Hugo Batista</dc:creator><description>Hi Jose&lt;br&gt;&lt;br&gt;Long time we don't see each other (tip: cgey - tranq). I think I was in the same session than you, although I didn't see you.&lt;br&gt;&lt;br&gt;Nice post. &lt;br&gt;&lt;br&gt;I would like just to comment some topics. In my opinion TDD should be considered as a demanded best practice. After adopting TDD I could never rollback. I think the best argument is “Try it”. BTW, to facilitate this approach, VS2005 should come with Unit Testing in all versions (I’m being repetitive, because everybody talks about the same), encouraging developers to use it as a practice.&lt;br&gt;Also I was a little surprised about “6 hours duration testing”, and I think unit testing is being driven too far in some organizations. I guess sometimes, people are confusing unit tests with load and functional tests. In my opinion,  the tests should run as fast as possible to provide the correct and expected implementation, and they also should run in granular tests, encouraging developers to do it. If tests take too long, the developer will avoid them. If some longer test should be done, then there should be two test runs, the developer’s tests and the daily build tests.&lt;br&gt;&lt;br&gt;Abra&amp;#231;o&lt;br&gt;</description></item><item><title>re: Unit testing session</title><link>http://blogs.msdn.com/josealmeida/archive/2004/07/05/173147.aspx#173511</link><pubDate>Tue, 06 Jul 2004 08:28:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:173511</guid><dc:creator>José Almeida</dc:creator><description>Hey, Hugo.&lt;br&gt;&lt;br&gt;Sorry I missed you.&lt;br&gt;&lt;br&gt;It's also my opinion that tests shouldn't take very long to run, or we might be discuraged to run them. i believe test-driven development is still in it's infancy. We haven't all the answers yet (as was evident by the questions on mock objects and testing databases, class internals and so forth). It's my opinion that the &amp;quot;industry&amp;quot; (I don't particularly like this metaphor, but I'll leace that for a further posting) is starting to absorbe these techniques and that it'll take a while for them to be adopted widely. As more and more developers incorporate the coding of unit tests into the development lifecycle, I believe some of the issues discussed in this session will reach consensus and, perhaps, we'll even see some unit testing patterns for them ;-)&lt;br&gt;&lt;br&gt;Abra&amp;#231;o</description></item></channel></rss>