<?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>Down Home Country Coding With Scott Selikoff and Jeanne Boyarsky &#187; testing</title>
	<atom:link href="http://www.selikoff.net/tag/testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.selikoff.net</link>
	<description>Java/J2EE Software Development and Technology Discussion Blog</description>
	<lastBuildDate>Thu, 29 Jul 2010 10:47:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>another reason % of time writing tests is meaningless</title>
		<link>http://www.selikoff.net/2010/02/27/another-reason-of-time-writing-tests-is-meaningless/</link>
		<comments>http://www.selikoff.net/2010/02/27/another-reason-of-time-writing-tests-is-meaningless/#comments</comments>
		<pubDate>Sat, 27 Feb 2010 22:18:13 +0000</pubDate>
		<dc:creator>Jeanne Boyarsky</dc:creator>
				<category><![CDATA[Development Process]]></category>
		<category><![CDATA[metrics]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/?p=1742</guid>
		<description><![CDATA[Earlier in the month, I blogged a response to – “What would you say is the average percentage of development time devoted to creating the unit test scripts?”.  As I was telling a friend about it, I realized that I missed an important point! The question also implies that development time is constant.  Or maybe [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2010/02/27/another-reason-of-time-writing-tests-is-meaningless/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>a response to &#8211; &#8220;What would you say is the average percentage of development time devoted to creating the unit test scripts?&#8221;</title>
		<link>http://www.selikoff.net/2010/02/14/a-response-to-what-would-you-say-is-the-average-percentage-of-development-time-devoted-to-creating-the-unit-test-scripts/</link>
		<comments>http://www.selikoff.net/2010/02/14/a-response-to-what-would-you-say-is-the-average-percentage-of-development-time-devoted-to-creating-the-unit-test-scripts/#comments</comments>
		<pubDate>Sun, 14 Feb 2010 18:11:25 +0000</pubDate>
		<dc:creator>Jeanne Boyarsky</dc:creator>
				<category><![CDATA[Development Process]]></category>
		<category><![CDATA[Java/J2EE]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/?p=1738</guid>
		<description><![CDATA[How long does it take to compile? We don&#8217;t ask that. It would be absurd. The fact that people ask how long unit testing takes mean they see it as an optional cost to be incurred. What I want to know is why they don&#8217;t ask for a similar accounting of the cost of NOT [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2010/02/14/a-response-to-what-would-you-say-is-the-average-percentage-of-development-time-devoted-to-creating-the-unit-test-scripts/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Refactoring JUnit 3.8 to 4.0 when hierarchy extends TestCase</title>
		<link>http://www.selikoff.net/2010/02/02/refactoring-junit-3-8-to-4-0-when-hierarchy-extends-testcase/</link>
		<comments>http://www.selikoff.net/2010/02/02/refactoring-junit-3-8-to-4-0-when-hierarchy-extends-testcase/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 04:01:19 +0000</pubDate>
		<dc:creator>Jeanne Boyarsky</dc:creator>
				<category><![CDATA[Java/J2EE]]></category>
		<category><![CDATA[junit]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/?p=1500</guid>
		<description><![CDATA[Problem: I want to start writing tests in JUnit 4.0, but I have a lot of tests in JUnit 3.8.  I can&#8217;t just start writing tests in 4.0, because I rely on common setup/assertions in my custom superclass which extends TestCase. (Which means JUnit will only look for 3.8 style tests) Solution: Create one or [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2010/02/02/refactoring-junit-3-8-to-4-0-when-hierarchy-extends-testcase/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>how testing can improve legacy code design</title>
		<link>http://www.selikoff.net/2009/05/10/how-testing-can-improve-legacy-code-design/</link>
		<comments>http://www.selikoff.net/2009/05/10/how-testing-can-improve-legacy-code-design/#comments</comments>
		<pubDate>Sun, 10 May 2009 22:01:59 +0000</pubDate>
		<dc:creator>Jeanne Boyarsky</dc:creator>
				<category><![CDATA[Development Process]]></category>
		<category><![CDATA[JavaRanch Forum Migration]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=948</guid>
		<description><![CDATA[There&#8217;s no shortage of articles on how TDD improves the design of new code.  That&#8217;s all well and good.  But what about legacy code? How it came up This weekend, I had occasion to make a few enhancements to the email sending project at JavaRanch.  The one that got me thinking about the design was [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2009/05/10/how-testing-can-improve-legacy-code-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
