<?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>testdriven.com &#187; Chapters</title>
	<atom:link href="http://www.testdriven.com/tag/chapters_post_tag/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.testdriven.com</link>
	<description>Wrangling quality out of chaos</description>
	<lastBuildDate>Thu, 26 Jan 2012 07:15:24 +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>Article series: Crafting Java Code with Test-Driven Development</title>
		<link>http://www.testdriven.com/2006/04/article_series_crafting_java_code_with_test_driven_development/</link>
		<comments>http://www.testdriven.com/2006/04/article_series_crafting_java_code_with_test_driven_development/#comments</comments>
		<pubDate>Wed, 12 Apr 2006 02:08:13 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=2046</guid>
		<description><![CDATA[A series of chapters patterned after Jeff Langr&#8217;s book, Agile Java: Crafting Code with Test-Driven Development: The basics &#8211; Getting started &#8211; Testing equality &#8211; Testing hash code &#8211; Shuffling and dealing &#8211; Handling exceptions &#8211; Refactoring tests &#8211; Adding some bulk Author: Jeff Langr Published: InformIT, 2005-2006 Other links to articles by Jeff Langr: [...]]]></description>
		<wfw:commentRss>http://www.testdriven.com/2006/04/article_series_crafting_java_code_with_test_driven_development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Agile Development with ICONIX Process</title>
		<link>http://www.testdriven.com/2005/07/agile_development_with_iconix_process/</link>
		<comments>http://www.testdriven.com/2005/07/agile_development_with_iconix_process/#comments</comments>
		<pubDate>Sat, 30 Jul 2005 12:23:58 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=2044</guid>
		<description><![CDATA[This book&#8217;s excerpt from Agile Development With Iconix Process provides an introduction to a process mixing the UML use case approach and Test-Driven Development. Authors: Doug Rosenberg, Matt Stephens &#38; Mark Collins-Cope Published: Methods and Tools, Spring 2005 link]]></description>
		<wfw:commentRss>http://www.testdriven.com/2005/07/agile_development_with_iconix_process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Agile Java: Assertions and Annotations [PDF]</title>
		<link>http://www.testdriven.com/2005/07/agile_java_assertions_and_annotations_pdf/</link>
		<comments>http://www.testdriven.com/2005/07/agile_java_assertions_and_annotations_pdf/#comments</comments>
		<pubDate>Sat, 02 Jul 2005 12:47:05 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=2030</guid>
		<description><![CDATA[J2SE 5.0 introduced a new facility known as annotations. Annotations are a metaprogramming facility that allow you to mark code with arbitrarily defined tags. The tags (generally) have no meaning to the Java compiler or runtime itself. Instead, other tools can interpret these tags. Examples of tools for which annotations might be useful include IDEs, [...]]]></description>
		<wfw:commentRss>http://www.testdriven.com/2005/07/agile_java_assertions_and_annotations_pdf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introduction to Refactoring to Patterns</title>
		<link>http://www.testdriven.com/2005/02/introduction_to_refactoring_to_patterns/</link>
		<comments>http://www.testdriven.com/2005/02/introduction_to_refactoring_to_patterns/#comments</comments>
		<pubDate>Sat, 12 Feb 2005 10:20:52 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=1851</guid>
		<description><![CDATA[Refactoring software by hand can be a real pain. So why not just automate the process? In this chapter, Joshua Kerievsky explains the whys and hows of refactoring, and why you shouldn&#8217;t trust that automated refactoring program. Author: Joshua Kerievsky Published: InformIT, January 28, 2005 Excerpted from Refactoring to Patternslink]]></description>
		<wfw:commentRss>http://www.testdriven.com/2005/02/introduction_to_refactoring_to_patterns/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test Driven Development: Programming by Intention [PDF]</title>
		<link>http://www.testdriven.com/2005/02/test_driven_development_programming_by_intention_pdf/</link>
		<comments>http://www.testdriven.com/2005/02/test_driven_development_programming_by_intention_pdf/#comments</comments>
		<pubDate>Fri, 04 Feb 2005 11:28:44 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=1826</guid>
		<description><![CDATA[Have you ever had to work on a piece of code and found that it was hard to understand? Maybe the logic was convoluted, the identifiers meaningless, or worse, misleading. You say there was documentation? Was it readable? Did it make sense? Was it up to date with the code? Are you sure? How do [...]]]></description>
		<wfw:commentRss>http://www.testdriven.com/2005/02/test_driven_development_programming_by_intention_pdf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Open Source .NET Development: ASpell.NET Case Study</title>
		<link>http://www.testdriven.com/2005/01/open_source_net_development_aspell_net_case_study/</link>
		<comments>http://www.testdriven.com/2005/01/open_source_net_development_aspell_net_case_study/#comments</comments>
		<pubDate>Thu, 27 Jan 2005 22:27:06 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=1809</guid>
		<description><![CDATA[This chapter is a simple but realistic case study of using Open Source tools in everyday development. In particular, this chapter uses ASpell, a commercial-caliber spell checking component that supports twenty-some different language dictionaries, as an example. Author: Brian Nantz Published: Jan 7, 2005 (Sample chapter extracted from Open Source .NET Development: Programming with NAnt, [...]]]></description>
		<wfw:commentRss>http://www.testdriven.com/2005/01/open_source_net_development_aspell_net_case_study/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Projects with Maven [PDF]</title>
		<link>http://www.testdriven.com/2005/01/managing_projects_with_maven_pdf/</link>
		<comments>http://www.testdriven.com/2005/01/managing_projects_with_maven_pdf/#comments</comments>
		<pubDate>Sun, 23 Jan 2005 15:45:01 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=1804</guid>
		<description><![CDATA[Maven started life as a subproject of Turbine, a Web application framework. It was born out of the need of its lead developer, Jason Van Zyl, to easily add in new pieces of functionality to his build process, such as unit testing or source metrics, both of which can be extremely important to a large [...]]]></description>
		<wfw:commentRss>http://www.testdriven.com/2005/01/managing_projects_with_maven_pdf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Changing Software and Legacy Code</title>
		<link>http://www.testdriven.com/2005/01/changing_software_and_legacy_code/</link>
		<comments>http://www.testdriven.com/2005/01/changing_software_and_legacy_code/#comments</comments>
		<pubDate>Thu, 20 Jan 2005 17:49:01 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=1803</guid>
		<description><![CDATA[The old adage, &#34;If it ain&#8217;t broke, don&#8217;t fix it,&#34; doesn&#8217;t necessarily apply in the case of technology. Projects continually require alterations, updates, and enhancements. This chapter outlines the nature of code change, and suggests some of the challenges to be faced when making these changes. Author: Michael Feathers Published: InformIT, January 14, 2005 Excerpted [...]]]></description>
		<wfw:commentRss>http://www.testdriven.com/2005/01/changing_software_and_legacy_code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Software Refactoring Workbook sample chapter: Measuring smells</title>
		<link>http://www.testdriven.com/2004/12/software_refactoring_workbook_sample_chapter_measuring_smells/</link>
		<comments>http://www.testdriven.com/2004/12/software_refactoring_workbook_sample_chapter_measuring_smells/#comments</comments>
		<pubDate>Thu, 09 Dec 2004 14:32:46 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=1740</guid>
		<description><![CDATA[You can think of these smells as being caught by a software metric. Each metric tends to catch different aspects of why code isn&#8217;t as good as it could be. Some metrics measure variants of code length; others try to measure the connections between methods or objects; others measure a distance from an ideal. Smells [...]]]></description>
		<wfw:commentRss>http://www.testdriven.com/2004/12/software_refactoring_workbook_sample_chapter_measuring_smells/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting started with test-driven development</title>
		<link>http://www.testdriven.com/2004/12/getting_started_with_test_driven_development/</link>
		<comments>http://www.testdriven.com/2004/12/getting_started_with_test_driven_development/#comments</comments>
		<pubDate>Wed, 08 Dec 2004 10:23:24 +0000</pubDate>
		<dc:creator>Eric Vautier</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Chapters]]></category>

		<guid isPermaLink="false">http://testdriven.tld/?p=1731</guid>
		<description><![CDATA[As software engineers, we often deal with performance requirements and end-user acceptance requirements. Why should the development process be any different? Quite frankly, it shouldn&#8217;t. Development projects should have realistic requirements for how long a build and test cycle should take. Metrics should be collected on a regular basis, so corrective action can be taken [...]]]></description>
		<wfw:commentRss>http://www.testdriven.com/2004/12/getting_started_with_test_driven_development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.263 seconds -->

