<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Developer Testing: The XPeriment</title>
<link>http://www.developertesting.com/</link>
<description>Developer Testing - A place to gain and share knowledge.</description>
<copyright>Copyright 2007</copyright>
<lastBuildDate>Wed, 12 Oct 2005 09:20:45 -0800</lastBuildDate>
<generator>http://www.movabletype.org/?v=3.16</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

" lastn="15">
<item>
<title>XP Stages of Acceptance</title>
<description><![CDATA[My friend <a href="http://www.developertesting.com/archives/individual_weblogs-kevin_lawrence-index.html">Kevin</a> is a very smart guy. He did a talk that was an intro to XP and one of his slides was "XP Stages of Acceptance":]]></description>
<link>http://www.developertesting.com/archives/month200510/20051012-XpStagesOfAcceptance.html</link>
<guid>http://www.developertesting.com/archives/month200510/20051012-XpStagesOfAcceptance.html</guid>
<category>Jeffrey Fredrick</category>
<pubDate>Wed, 12 Oct 2005 09:20:45 -0800</pubDate>

</item>
" lastn="15">
<item>
<title>Cockburn, Goal Displacement, and Running Tested Features</title>
<description><![CDATA[On Friday <a href="http://alistair.cockburn.us/">Alistair Cockburn</a> posted an article with the provocative title <a href="http://alistair.cockburn.us/crystal/articles/aih/areiterationshazardous.htm">"Are Iterations Hazardous to Your Project?"...</a>]]></description>
<link>http://www.developertesting.com/archives/month200509/20050910-CockburnGoalDisplacementAndRunningTestedFeatures.html</link>
<guid>http://www.developertesting.com/archives/month200509/20050910-CockburnGoalDisplacementAndRunningTestedFeatures.html</guid>
<category>Jeffrey Fredrick</category>
<pubDate>Sat, 10 Sep 2005 10:14:48 -0800</pubDate>

</item>
" lastn="15">
<item>
<title>Patterns for Iteration Retrospectives</title>
<description><![CDATA[<a href="http://weblogs.java.net/blog/wwake/">Bill Wake</a>'s post to the extreme programming mailing list caught my eye...
]]></description>
<link>http://www.developertesting.com/archives/month200509/20050908-PatternsForIterationRetrospectives.html</link>
<guid>http://www.developertesting.com/archives/month200509/20050908-PatternsForIterationRetrospectives.html</guid>
<category>Jeffrey Fredrick</category>
<pubDate>Thu, 08 Sep 2005 15:06:34 -0800</pubDate>

</item>
" lastn="15">
<item>
<title>Relentless Testing and The XP Oath</title>
<description><![CDATA[James Shore has reminded us what the extreme version of developer testing is about:
<blockquote>We will test everything that could possibly break. We will have tests at the customer level as well as at the programmer level. We will write our tests before we write our code, possibly moments before. We will automate our tests and provide a binary "pass/fail" mechanism for evaluating the result.</blockquote>
Read the rest of his "Extreme Programmers Oath" over <a href="http://www.jamesshore.com/Blog/An-Extreme-Stake-in-the-Ground.html">here</a>.]]></description>
<link>http://www.developertesting.com/archives/month200508/20050823-RelentlessTestingAndTheXpOath.html</link>
<guid>http://www.developertesting.com/archives/month200508/20050823-RelentlessTestingAndTheXpOath.html</guid>
<category>Jeffrey Fredrick</category>
<pubDate>Tue, 23 Aug 2005 21:31:14 -0800</pubDate>

</item>
" lastn="15">
<item>
<title>XPeriment Findings</title>
<description><![CDATA[In January, we described <a href="/archives/month200401/20040121-TheXPeriment.html">The XPeriment</a> we were beginning, and I felt it was time to revisit our hypothesis and see how well our predictions worked out and mention a couple surprise lessons we learned along the way.]]></description>
<link>http://www.developertesting.com/archives/month200405/20040514-XPerimentFindings.html</link>
<guid>http://www.developertesting.com/archives/month200405/20040514-XPerimentFindings.html</guid>
<category>Jeffrey Fredrick</category>
<pubDate>Fri, 14 May 2004 17:11:28 -0800</pubDate>

</item>
" lastn="15">
<item>
<title>In Tests We Trust?</title>
<description>I had an interesting experience a couple of weeks ago that brought home the influence of developer testing on trust in someone else&apos;s code. After reflecting, I think that being able to show an effective base of developer tests is -- or should be -- the most influential proxy for quality code.</description>
<link>http://www.developertesting.com/archives/month200403/20040315-InTestsWeTrust.html</link>
<guid>http://www.developertesting.com/archives/month200403/20040315-InTestsWeTrust.html</guid>
<category>Jeffrey Fredrick</category>
<pubDate>Mon, 15 Mar 2004 16:05:23 -0800</pubDate>

</item>
" lastn="15">
<item>
<title>Fight Complexity with Complexity</title>
<description>We were using method and class and package names as keys to the various data structures that store test results and coverage data. Agitator told us that if you pass the string &quot;123%%^*abc&quot; to a method that expects a class name, it throws an IllegalArgumentException. &quot;Well, duh!&quot; we said and marked it expected. We added a factory to generate a variety of good and bad class names and got on with the task at hand.</description>
<link>http://www.developertesting.com/archives/month200403/20040308-FightComplexityWithComplexity.html</link>
<guid>http://www.developertesting.com/archives/month200403/20040308-FightComplexityWithComplexity.html</guid>
<category>Kevin Lawrence</category>
<pubDate>Mon, 08 Mar 2004 17:17:27 -0800</pubDate>

</item>
" lastn="15">
<item>
<title>Test-Driven Development and Agitator-Driven Refactoring</title>
<description><![CDATA[We've had a good solid month of development experience on <a href="/archives/month200401/20040121-TheXPeriment.html">The eXperiment</a> now and things are going rather well. All of our code is written test first by pairs, we refactor without mercy, and we continuously integrate. Part of our continuous integration is continuous agitation, and it is on that front that we've had the biggest surprise.]]></description>
<link>http://www.developertesting.com/archives/month200402/20040226-TestDrivenDevelopmentAndAgitatorDrivenRefactoring.html</link>
<guid>http://www.developertesting.com/archives/month200402/20040226-TestDrivenDevelopmentAndAgitatorDrivenRefactoring.html</guid>
<category>Jeffrey Fredrick</category>
<pubDate>Thu, 26 Feb 2004 15:52:48 -0800</pubDate>

</item>
" lastn="15">
<item>
<title>The XPeriment</title>
<description><![CDATA[When talking about developer testing in Java, the conversation often shifts to XP and other <a href="http://agilemanifesto.org/">Agile</a> <a href="http://www.martinfowler.com/articles/newMethodology.html">methods</a>. Thus it happens that we get asked how <a href="/archives/month200312/20031227-ManagedDeveloperTesting.html">Managed Developer Testing</a> works with a team doing XP. We feel there is a good story to tell there, but it isn't one we can speak to from first-hand experience. Combine those queries with an "XP-curious" <a href="http://www.agitar.com/company/000009.html#alberto">CTO</a> and a couple of internal XP advocates and it is time for an experiment.]]></description>
<link>http://www.developertesting.com/archives/month200401/20040121-TheXPeriment.html</link>
<guid>http://www.developertesting.com/archives/month200401/20040121-TheXPeriment.html</guid>
<category>Jeffrey Fredrick</category>
<pubDate>Wed, 21 Jan 2004 14:26:23 -0800</pubDate>

</item>


</channel>
</rss>