<?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>Project Oriel &#187; testing</title>
	<atom:link href="http://www.edstrom.net/blog/archive/tag/testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edstrom.net/blog</link>
	<description>Embracing Change</description>
	<lastBuildDate>Fri, 10 Sep 2010 13:41:56 +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>Time Bombs</title>
		<link>http://www.edstrom.net/blog/archive/time-bombs/</link>
		<comments>http://www.edstrom.net/blog/archive/time-bombs/#comments</comments>
		<pubDate>Sat, 29 May 2010 14:49:16 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[quotes]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1140</guid>
		<description><![CDATA[Ran across this quote recently, thought you might enjoy it: &#8220;Don&#8217;t call your defects &#8216;bugs&#8217;. Call them &#8216;time bombs&#8217; instead.&#8221; - Watts S. Humphrey From Wikipedia: &#8220;Watts S. Humphrey (born 1927) is an American software engineer, key thinker in the discipline of software engineering, and is often called the father of software quality.&#8221; He has [...]]]></description>
			<content:encoded><![CDATA[<p>Ran across this quote recently, thought you might enjoy it:</p>
<blockquote><p>&#8220;Don&#8217;t call your defects &#8216;bugs&#8217;. Call them &#8216;time bombs&#8217; instead.&#8221;<br />
- Watts S. Humphrey</p></blockquote>
<p>From Wikipedia: &#8220;<a href="http://en.wikipedia.org/wiki/Watts_Humphrey">Watts S. Humphrey</a> (born 1927) is an American software engineer, key thinker in the discipline of software engineering, and is often called the father of software quality.&#8221;</p>
<p>He has a recent book out that looks like it could be good, <em>Reflections on Management: How to Manage Your Software Projects, Your  Teams, Your Boss, and Yourself</em>.  Has anyone read it?</p>
<p>[via <a href="https://twitter.com/jurgenappelo/status/13809454465">@jurgenappelo</a>]</p>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 100px; width: 1px; height: 1px; overflow: hidden;">&#8220;Don&#8217;t call your defects &#8216;bugs&#8217;. Call them &#8216;time bombs&#8217; instead.&#8221; &#8211; Watts S. Humphrey</div>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/time-bombs/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Are you testing or checking?</title>
		<link>http://www.edstrom.net/blog/archive/are-you-testing-or-checking/</link>
		<comments>http://www.edstrom.net/blog/archive/are-you-testing-or-checking/#comments</comments>
		<pubDate>Mon, 25 Jan 2010 03:47:44 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=992</guid>
		<description><![CDATA[Vikas Hazrati posts an interesting thought about testing vs. checking at InfoQ: &#8220;Checking is something that we do with the motivation of confirming existing beliefs. [...] Testing is something that we do with the motivation of finding new information.&#8221; So when you &#8220;test&#8221; your software, are you really testing? Or are you just checking?]]></description>
			<content:encoded><![CDATA[<p>Vikas Hazrati posts an interesting thought about <a href="http://www.infoq.com/news/2009/12/testing-or-checking">testing vs. checking</a> at InfoQ:</p>
<blockquote><p>&#8220;<strong>Checking</strong> is something that we do with the motivation of <em>confirming existing beliefs</em>. [...] <strong>Testing</strong> is something that we do with the motivation of <em>finding new information</em>.&#8221;</p></blockquote>
<p>So when you &#8220;test&#8221; your software, are you really testing? Or are you just checking?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/are-you-testing-or-checking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical Debt</title>
		<link>http://www.edstrom.net/blog/archive/technical-debt/</link>
		<comments>http://www.edstrom.net/blog/archive/technical-debt/#comments</comments>
		<pubDate>Mon, 30 Jun 2008 02:49:37 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=190</guid>
		<description><![CDATA[Johanna Rothman writes about tracking the stuff you can&#8217;t fix today, but need to someday: Technical debt needs to be as visible as everything else. Maybe more so, because the more debt you have, the slower any future development will be.]]></description>
			<content:encoded><![CDATA[<p>Johanna Rothman <a href="http://jrothman.com/blog/mpd/2008/06/make-technical-debt-visible.html">writes</a> about tracking the stuff you can&#8217;t fix today, but need to someday:</p>
<blockquote><p>Technical debt needs to be as visible as everything else. Maybe more so, because the more debt you have, the slower any future development will be.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/technical-debt/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
