<?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; Embedded TDD</title>
	<atom:link href="http://www.renaissancesoftware.net/blog/archives/tag/embedded-tdd/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>Agile Design and Embedded</title>
		<link>http://www.renaissancesoftware.net/blog/archives/81</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/81#comments</comments>
		<pubDate>Thu, 12 Nov 2009 12:31:03 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Agile Embedded]]></category>
		<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Evolutionary Design]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[Embedded Agile]]></category>
		<category><![CDATA[TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=81</guid>
		<description><![CDATA[One important realization on the journey from a BDUF approach to an iterative and agile approach is that design is never done. Designs evolve. The waterfall emphasis has been to unnaturally try to control software physics by imposing requirements freezes and burdensome change control. The process of developing software is part science and part creative. [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/81/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Three Steps to less duplication</title>
		<link>http://www.renaissancesoftware.net/blog/archives/13</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/13#comments</comments>
		<pubDate>Wed, 26 Mar 2008 15:46:40 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[C]]></category>
		<category><![CDATA[CppUTest]]></category>
		<category><![CDATA[TDD C]]></category>
		<category><![CDATA[Test Driven Development C]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=13</guid>
		<description><![CDATA[Like I said in my previous blog, doing all this embedded C makes me miss constructors. I&#8217;ve got a three step plan to make the lack of constructors less painful. In the previous article, we discussed the problem of duplicate setup data, and all the duplicate effort to go along with it. In this article [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/13/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>I miss constructors</title>
		<link>http://www.renaissancesoftware.net/blog/archives/12</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/12#comments</comments>
		<pubDate>Thu, 13 Mar 2008 14:04:14 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[C]]></category>
		<category><![CDATA[CppUTest]]></category>
		<category><![CDATA[TDD C]]></category>
		<category><![CDATA[Test Driven Development C]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=12</guid>
		<description><![CDATA[I&#8217;m working with a few teams evolving a large complex legacy embedded C application. (Whoa! That is a lot of modifiers on application.) We are trying to get unit tests in place. I think there is some 20 year old code here. And this application is not going away anytime soon. So adding tests is [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/12/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Now I&#8217;ll really use test driven development to write device driver code</title>
		<link>http://www.renaissancesoftware.net/blog/archives/8</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/8#comments</comments>
		<pubDate>Thu, 06 Mar 2008 10:38:46 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[Embedded Agile]]></category>
		<category><![CDATA[TDD]]></category>
		<category><![CDATA[TDD Device Driver]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=8</guid>
		<description><![CDATA[In the last article, I added tests to existing code. So I did not really do Test Driven Development. I did Test After Development. Let&#8217;s do some TDD now and design the block erase function. I&#8217;ll go from the spec, to the test to the code. The data sheet for the device describes block erase [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/8/feed</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Who says you can’t test drive a device driver?</title>
		<link>http://www.renaissancesoftware.net/blog/archives/7</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/7#comments</comments>
		<pubDate>Mon, 18 Feb 2008 01:53:29 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Agile Embedded]]></category>
		<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[Embedded Agile]]></category>
		<category><![CDATA[TDD]]></category>
		<category><![CDATA[TDD Device Driver]]></category>

		<guid isPermaLink="false">http://blog.renaissancesoftware.net/?p=7</guid>
		<description><![CDATA[I keep hearing that you can&#8217;t write unit tests for device drivers. I don&#8217;t believe that&#8217;s true. To disprove this claim, I thought I would find a device driver and write some unit tests for it. This blog posting shows what device driver unit tests look line. I found a flash memory driver at the [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/7/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

