<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>James Grenning's Blog &#187; Uncategorized</title>
	<atom:link href="http://www.renaissancesoftware.net/blog/archives/category/uncategorized/feed" rel="self" type="application/rss+xml" />
	<link>http://www.renaissancesoftware.net/blog</link>
	<description>Blogging about Agile Development, especially embedded.  Follow me on twitter: jwgrenning</description>
	<lastBuildDate>Thu, 12 Jan 2012 00:59:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Manual Test is Unsustainable</title>
		<link>http://www.renaissancesoftware.net/blog/archives/206</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/206#comments</comments>
		<pubDate>Thu, 12 Jan 2012 00:59:40 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[automation]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Unit Testing]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=206</guid>
		<description><![CDATA[Creating automated tests can be very difficult, especially when the code has gotten long in the tooth and was not created with automated tests to begin with. Many product development teams don&#8217;t invest in automated tests. They think they cannot afford them. They think their product is different and can&#8217;t be manually tested. This thinking [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/206/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Mocking the &#8216;asm&#8217; directive with CppUMock</title>
		<link>http://www.renaissancesoftware.net/blog/archives/143</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/143#comments</comments>
		<pubDate>Fri, 03 Jun 2011 17:23:18 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=143</guid>
		<description><![CDATA[My last article featured a hand crafted a spy to monitor asm directives. Now let&#8217;s use CppUMock (the mock support companion CppUTest) to create a mock version of asm. Starting with the test (where else would you start), MockAsm works like this: #include &#34;CppUTest/TestHarness.h&#34; #include &#34;CppUTestExt/MockSupport.h&#34; &#160; extern &#34;C&#34; &#123; #include &#34;MockAsm.h&#34; &#125; &#160; TEST_GROUP&#40;MockAsm&#41; [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/143/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Legacy Code Change &#8211; a Boy Scout Adds Tests</title>
		<link>http://www.renaissancesoftware.net/blog/archives/96</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/96#comments</comments>
		<pubDate>Tue, 03 Aug 2010 19:26:01 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=96</guid>
		<description><![CDATA[Here is a legacy code change policy for a team adopting TDD that has a legacy code base: Test-drive new code Add tests to legacy code before modification Test-drive changes to legacy code Refactoring without tests is dangerous; with all the details we must keep straight, a mistake is easy to make. How many code [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/96/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Deep Agile Panel Questions &#8211; Change</title>
		<link>http://www.renaissancesoftware.net/blog/archives/43</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/43#comments</comments>
		<pubDate>Wed, 06 May 2009 14:41:05 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Agile Embedded]]></category>
		<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=43</guid>
		<description><![CDATA[Prior to the Deep Agile conference, I received a number of questions about getting people to change, to try new things. Change is hard. People need to be motivated to change. &#8220;If it ain’t broke, don’t fix it&#8221; they say. But there is always some things that are broken. First there needs to be awareness/acceptance [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/43/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Deep Agile Embedded Panel Questions &#8211; Hardware</title>
		<link>http://www.renaissancesoftware.net/blog/archives/42</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/42#comments</comments>
		<pubDate>Fri, 01 May 2009 22:14:20 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=42</guid>
		<description><![CDATA[Last weekend was the Deep Agile Embedded Conference that I participated in. In this article I&#8217;ll answer some of the panel questions related to concurrent hardware development. There seems to be a theme here, because the hardware is involved, an embedded development team really can&#8217;t be agile. That&#8217;s not my point of view, or my [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/42/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t Let Embedded Tool Chain Slow You Down.</title>
		<link>http://www.renaissancesoftware.net/blog/archives/41</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/41#comments</comments>
		<pubDate>Wed, 01 Apr 2009 22:55:15 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[TDD]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=41</guid>
		<description><![CDATA[During my TDD session at the Embedded Systems Conference yesterday, I did a demo. Before the demo, I make the case for TDD as a way to prevent bugs (see Physics of TDD). For the live demo I usually code on my mac and run the tests there as well. The question always comes up: [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/41/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Agile?  How do I learn more?</title>
		<link>http://www.renaissancesoftware.net/blog/archives/30</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/30#comments</comments>
		<pubDate>Fri, 23 Jan 2009 18:34:37 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=30</guid>
		<description><![CDATA[LinkedIn is fun. Every now and then a person from the past pops in. A colleague from my early days at Teradyne had just heard about agile and she asked me what it was and how to learn more. Here&#8217;s what I told her. I started with Extreme Programming Explained in 1999. A lot has [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/30/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tests vs. Short Term Cache Between Your Ears</title>
		<link>http://www.renaissancesoftware.net/blog/archives/15</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/15#comments</comments>
		<pubDate>Mon, 05 May 2008 23:23:03 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Learning Tests]]></category>
		<category><![CDATA[TDD]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=15</guid>
		<description><![CDATA[You have someone else&#8217;s code. You have to use it. To use it you have to learn it. If the code had automated unit tests you could read the unit tests to see how the code behaves. But, it probably does not have unit tests. So, you read the documentation. The documentation usually leaves some [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/15/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

