<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Making unittest life better &#8211; whats next?</title>
	<atom:link href="http://oduinn.com/blog/2009/03/25/making-unittest-life-better-whats-next/feed/" rel="self" type="application/rss+xml" />
	<link>http://oduinn.com/blog/2009/03/25/making-unittest-life-better-whats-next/</link>
	<description></description>
	<lastBuildDate>Fri, 27 Jan 2012 15:12:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John O&#8217;Duinn&#8217;s Soapbox &#187; Welcome (back) Lukas!</title>
		<link>http://oduinn.com/blog/2009/03/25/making-unittest-life-better-whats-next/#comment-31725</link>
		<dc:creator>John O&#8217;Duinn&#8217;s Soapbox &#187; Welcome (back) Lukas!</dc:creator>
		<pubDate>Thu, 21 May 2009 15:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2009/03/25/making-unittest-life-better-whats-next/#comment-31725</guid>
		<description>[...] If you&#8217;ve never met Lukas, you should know that last summer, Lukas arrived for her internship, and had barely unpacked when we handed her the entire unittest infrastructure without warning. With very little guidance, she took it all on. Lukas worked non-stop stabilizing and streamlining machine configs in a million-and-one little details, chasing intermittent unittest failures to figure out if they were caused by code bugs, testware bugs, RelEng bugs or IT bugs&#8230; or a combination! She was so great, we hired her as a part-time contractor when she was heading back to Seneca. In that role, she worked with catlee and myself to consolidate all the build and unittest machines into one shared pool (details here). This project massively simplified life in RelEng, improved end-to-end turnaround time for developers; more importantly, it was a pre-req to getting unittests running on TryServer, and also to separating out build from unittest for faster turnaround times (details here, here and here). All massive stuff. [...]</description>
		<content:encoded><![CDATA[<p>[...] If you&#8217;ve never met Lukas, you should know that last summer, Lukas arrived for her internship, and had barely unpacked when we handed her the entire unittest infrastructure without warning. With very little guidance, she took it all on. Lukas worked non-stop stabilizing and streamlining machine configs in a million-and-one little details, chasing intermittent unittest failures to figure out if they were caused by code bugs, testware bugs, RelEng bugs or IT bugs&#8230; or a combination! She was so great, we hired her as a part-time contractor when she was heading back to Seneca. In that role, she worked with catlee and myself to consolidate all the build and unittest machines into one shared pool (details here). This project massively simplified life in RelEng, improved end-to-end turnaround time for developers; more importantly, it was a pre-req to getting unittests running on TryServer, and also to separating out build from unittest for faster turnaround times (details here, here and here). All massive stuff. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John O&#8217;Duinn&#8217;s Soapbox &#187; Improving end-to-end times</title>
		<link>http://oduinn.com/blog/2009/03/25/making-unittest-life-better-whats-next/#comment-29810</link>
		<dc:creator>John O&#8217;Duinn&#8217;s Soapbox &#187; Improving end-to-end times</dc:creator>
		<pubDate>Mon, 27 Apr 2009 07:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2009/03/25/making-unittest-life-better-whats-next/#comment-29810</guid>
		<description>[...] how long unittests take to run, and how unittests are being changed to run suites concurrently on separate slaves. See details here. [...]</description>
		<content:encoded><![CDATA[<p>[...] how long unittests take to run, and how unittests are being changed to run suites concurrently on separate slaves. See details here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

