<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Code Contracts and Pex: Power Charge Your Assertions and Unit Tests</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/martinesmann/Code-Contracts-and-Pex-Power-Charge-Your-Assertions-and-Unit-Tests/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/552185_100x75.jpg</url>
		<title>Channel 9 - Code Contracts and Pex: Power Charge Your Assertions and Unit Tests</title>
		<link></link>
	</image>
	<description>
By&amp;nbsp;Nikolai Tillmann and&amp;nbsp;&amp;nbsp;Mike BarnettLearn how&amp;nbsp;Code Contracts provides a set of tools for design-by-contract programming and how Pex is an advanced unit-testing tool that uses automated program exploration to intelligently create unit tests with high code coverage.&amp;nbsp;
See how they work together so that your code has fewer defects. Learn about new features for Code Contracts including automatic documentation generation, call-site checking for components and reference assemblies for the .NET Framework and for Pex including a light-weight mocking framework, improved support for large code
 bases, and more thorough test input generation.Links:PEX //

Code Contracts // 
Mike Barnett // 
Nikolai Tillmann&amp;nbsp;//&amp;nbsp;MDCC //
DPE DK 
</description>
	<link></link>
	<language>en</language>
	<pubDate>Fri, 24 May 2013 16:19:06 GMT</pubDate>
	<lastBuildDate>Fri, 24 May 2013 16:19:06 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Code Contracts and Pex: Power Charge Your Assertions and Unit Tests</title>
		<description>
			<![CDATA[
<p>Near the end now and I really need to ask:</p>
<p>Witch one is nicer in your opinion ?</p>
<p>1. MDataTime.NowGet() = () =&gt; DateTime.Now;</p>
<p>2. Isolate.WhenCalled(()=&gt; DareTime.Now()).WillReturn(DateTime.Now);</p>
<p>&nbsp;</p>
<p>And you know what's great, WillReturn can have a delegate also, but it does not have too all the time.</p>
<p>posted by calinus</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/martinesmann/Code-Contracts-and-Pex-Power-Charge-Your-Assertions-and-Unit-Tests#c634108395130000000</link>
		<pubDate>Sun, 30 May 2010 18:05:13 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/martinesmann/Code-Contracts-and-Pex-Power-Charge-Your-Assertions-and-Unit-Tests#c634108395130000000</guid>
		<dc:creator>calinus</dc:creator>
	</item>
	<item>
		<title>Re: Code Contracts and Pex: Power Charge Your Assertions and Unit Tests</title>
		<description>
			<![CDATA[
<p>&gt; Witch one is nicer in your opinion ?</p>
<p>Let's say that both are not as good as they could be. Language/CLR support would be the ultimate solution.</p>
<p>&nbsp;</p>
<p>ps: 1. will result in a stackoverflow since the delegate will recursively call itself. Not sure about 2.</p>
<p>posted by peli</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/martinesmann/Code-Contracts-and-Pex-Power-Charge-Your-Assertions-and-Unit-Tests#c634109608530000000</link>
		<pubDate>Tue, 01 Jun 2010 03:47:33 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/martinesmann/Code-Contracts-and-Pex-Power-Charge-Your-Assertions-and-Unit-Tests#c634109608530000000</guid>
		<dc:creator>peli</dc:creator>
	</item>
</channel>
</rss>