<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Rapid vs. Hyper-Rapid Testing</title>
	<atom:link href="http://www.satisfice.com/blog/archives/9/feed" rel="self" type="application/rss+xml" />
	<link>http://www.satisfice.com/blog/archives/9</link>
	<description>The Consulting Software Tester</description>
	<lastBuildDate>Fri, 03 Feb 2012 10:21:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dan Meservy</title>
		<link>http://www.satisfice.com/blog/archives/9/comment-page-1#comment-239858</link>
		<dc:creator>Dan Meservy</dc:creator>
		<pubDate>Thu, 28 Jan 2010 16:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://12.165.213.55/blog/?p=9#comment-239858</guid>
		<description>Like Aaron, I feel a little behind the times on commenting on this blog post.  I was hired as a software tester in November, and have been scouring the web for good resources.  Most of the books I&#039;ve read thus far on testing are rather vague (as some say the actual art of testing is).  I&#039;ve discovered this site where I can now get a certain level of knowledge, then tweak it to fit my personal situation.  Thanks, James, for a concise example of how to hit a program quick and hard.  I can see these heuristics being applied to interview questions, etc.  Thank you!</description>
		<content:encoded><![CDATA[<p>Like Aaron, I feel a little behind the times on commenting on this blog post.  I was hired as a software tester in November, and have been scouring the web for good resources.  Most of the books I&#8217;ve read thus far on testing are rather vague (as some say the actual art of testing is).  I&#8217;ve discovered this site where I can now get a certain level of knowledge, then tweak it to fit my personal situation.  Thanks, James, for a concise example of how to hit a program quick and hard.  I can see these heuristics being applied to interview questions, etc.  Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Hodder</title>
		<link>http://www.satisfice.com/blog/archives/9/comment-page-1#comment-114854</link>
		<dc:creator>Aaron Hodder</dc:creator>
		<pubDate>Thu, 20 Mar 2008 02:04:57 +0000</pubDate>
		<guid isPermaLink="false">http://12.165.213.55/blog/?p=9#comment-114854</guid>
		<description>Four years is a long time to leave a comment after a post, but I have to say that this is the most concise guide to exploratory testing I have ever seen.  If I ever get stuck or run out of inspiration for what to do next, I search for this article, and find it kick starts the creative juices again.

Thanks James
&lt;em&gt;
[James&#039; Reply: Thanks, but be careful. This is not a description of exploratory testing. This is a description of an approach to testing that may or may not be exploratory, but usually is &lt;strong&gt;very&lt;/strong&gt; exploratory. I now call this kind of testing &quot;quick-testing&quot; as in &quot;I&#039;m going to do some quick-tests now.&quot; We can imagine highly scripted quick-tests, too. When people confuse quick-testing with exploratory testing, they miss out on all the slow, careful, and deep forms of exploratory testing.]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Four years is a long time to leave a comment after a post, but I have to say that this is the most concise guide to exploratory testing I have ever seen.  If I ever get stuck or run out of inspiration for what to do next, I search for this article, and find it kick starts the creative juices again.</p>
<p>Thanks James<br />
<em><br />
[James' Reply: Thanks, but be careful. This is not a description of exploratory testing. This is a description of an approach to testing that may or may not be exploratory, but usually is <strong>very</strong> exploratory. I now call this kind of testing "quick-testing" as in "I'm going to do some quick-tests now." We can imagine highly scripted quick-tests, too. When people confuse quick-testing with exploratory testing, they miss out on all the slow, careful, and deep forms of exploratory testing.]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joaquin BolaÃƒÂ±os Vargas</title>
		<link>http://www.satisfice.com/blog/archives/9/comment-page-1#comment-13</link>
		<dc:creator>Joaquin BolaÃƒÂ±os Vargas</dc:creator>
		<pubDate>Tue, 17 Feb 2004 17:08:49 +0000</pubDate>
		<guid isPermaLink="false">http://12.165.213.55/blog/?p=9#comment-13</guid>
		<description>Right now, sometimes our applications have errors in production time that we couldn&#039;t get because of for example the programmer forgot to replicated the new code into another module.  However the black box testing didn&#039;t catch that error.  So i have the doubt about when it is strictly necessary to do White Box Testing...

</description>
		<content:encoded><![CDATA[<p>Right now, sometimes our applications have errors in production time that we couldn&#8217;t get because of for example the programmer forgot to replicated the new code into another module.  However the black box testing didn&#8217;t catch that error.  So i have the doubt about when it is strictly necessary to do White Box Testing&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Surya</title>
		<link>http://www.satisfice.com/blog/archives/9/comment-page-1#comment-12</link>
		<dc:creator>Surya</dc:creator>
		<pubDate>Wed, 04 Feb 2004 21:44:30 +0000</pubDate>
		<guid isPermaLink="false">http://12.165.213.55/blog/?p=9#comment-12</guid>
		<description>Hi, I&#039;m a developer trying to decide whether to be a full-time tester or not. Like u i am getting tired of this long cycle of production coding. Ur website/articles gave me a lot of insight into the world of testing. Thanks. 
Now I&#039;m going to apply the above steps to these fields to check if I can crash this page!
hehe Thanks a lot,
Surya</description>
		<content:encoded><![CDATA[<p>Hi, I&#8217;m a developer trying to decide whether to be a full-time tester or not. Like u i am getting tired of this long cycle of production coding. Ur website/articles gave me a lot of insight into the world of testing. Thanks.<br />
Now I&#8217;m going to apply the above steps to these fields to check if I can crash this page!<br />
hehe Thanks a lot,<br />
Surya</p>
]]></content:encoded>
	</item>
</channel>
</rss>

