<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Monkey business value</title>
	<atom:link href="http://dannorth.net/2007/02/15/monkey-business-value/feed/" rel="self" type="application/rss+xml" />
	<link>http://dannorth.net/2007/02/15/monkey-business-value/</link>
	<description>embracing uncertainty</description>
	<lastBuildDate>Thu, 02 Feb 2012 20:47:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Dan North</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7817</link>
		<dc:creator><![CDATA[Dan North]]></dc:creator>
		<pubDate>Sun, 07 Sep 2008 18:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7817</guid>
		<description><![CDATA[Hi Henrik.

You are right of course. Exploratory testing is much more than monkey testing - it&#039;s about using the application in different and unexpected ways to see how it behaves outside of the expected use cases. Monkey testing is one tiny subset of this, and the idea behind something like rmonkey is to automate this class of exploratory (meaning out-of-the-ordinary) testing and free up the testers to spend their time exploring other aspects of the application&#039;s behaviour.]]></description>
		<content:encoded><![CDATA[<p>Hi Henrik.</p>
<p>You are right of course. Exploratory testing is much more than monkey testing &#8211; it&#8217;s about using the application in different and unexpected ways to see how it behaves outside of the expected use cases. Monkey testing is one tiny subset of this, and the idea behind something like rmonkey is to automate this class of exploratory (meaning out-of-the-ordinary) testing and free up the testers to spend their time exploring other aspects of the application&#8217;s behaviour.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik Andersson</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7816</link>
		<dc:creator><![CDATA[Henrik Andersson]]></dc:creator>
		<pubDate>Sun, 31 Aug 2008 18:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7816</guid>
		<description><![CDATA[I see that you are a developer and to a tester :)
Most of the developer says that test automation is solution to everything, but that okej for me to think that.
But comparing Exploratory Testing with &quot;monkey testing&quot;, is little bit to much. E.T is more the punching the keyboard to get randomly input. So please don&#039;t E.T for monkey testing.

Best Regards
Henrik]]></description>
		<content:encoded><![CDATA[<p>I see that you are a developer and to a tester :)<br />
Most of the developer says that test automation is solution to everything, but that okej for me to think that.<br />
But comparing Exploratory Testing with &#8220;monkey testing&#8221;, is little bit to much. E.T is more the punching the keyboard to get randomly input. So please don&#8217;t E.T for monkey testing.</p>
<p>Best Regards<br />
Henrik</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sai</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7815</link>
		<dc:creator><![CDATA[Sai]]></dc:creator>
		<pubDate>Thu, 06 Sep 2007 13:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7815</guid>
		<description><![CDATA[Stochastic monkey testing is good but it also better to give it a sense of direction using model. I am currently working on the model based testing tool using Ruby. I had tried this with Python.]]></description>
		<content:encoded><![CDATA[<p>Stochastic monkey testing is good but it also better to give it a sense of direction using model. I am currently working on the model based testing tool using Ruby. I had tried this with Python.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sai</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7814</link>
		<dc:creator><![CDATA[Sai]]></dc:creator>
		<pubDate>Thu, 06 Sep 2007 13:53:19 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7814</guid>
		<description><![CDATA[I suppose stochastic monkey testing is good and effective. But giving it a sense of direction is also good with the help of model of the application. I am planning for a model based testing tool using Ruby. I have already tried this with Python and was succesful.]]></description>
		<content:encoded><![CDATA[<p>I suppose stochastic monkey testing is good and effective. But giving it a sense of direction is also good with the help of model of the application. I am planning for a model based testing tool using Ruby. I have already tried this with Python and was succesful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Campbell</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7813</link>
		<dc:creator><![CDATA[Steve Campbell]]></dc:creator>
		<pubDate>Mon, 30 Apr 2007 18:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7813</guid>
		<description><![CDATA[This looks like some of the work being done on testing at Microsoft, although they have gotten much further than you suggest.  http://research.microsoft.com/Pex/]]></description>
		<content:encoded><![CDATA[<p>This looks like some of the work being done on testing at Microsoft, although they have gotten much further than you suggest.  <a href="http://research.microsoft.com/Pex/" rel="nofollow">http://research.microsoft.com/Pex/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: silk and spinach</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7812</link>
		<dc:creator><![CDATA[silk and spinach]]></dc:creator>
		<pubDate>Thu, 01 Mar 2007 12:09:43 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7812</guid>
		<description><![CDATA[carnival of the agilists, 1-mar-07...

This issue of the carnival consists entirely of Britblogs!...]]></description>
		<content:encoded><![CDATA[<p>carnival of the agilists, 1-mar-07&#8230;</p>
<p>This issue of the carnival consists entirely of Britblogs!&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dancingmango &#187; This impatient monkey</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7811</link>
		<dc:creator><![CDATA[dancingmango &#187; This impatient monkey]]></dc:creator>
		<pubDate>Wed, 21 Feb 2007 10:20:36 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7811</guid>
		<description><![CDATA[[...] The developer tuts, &#8220;it&#8217;s your own fault&#8221; he says, &#8220;you broke it with your impatience&#8221;.  And that is why Dan North’s recent blog about Monkey Testing fills me with happiness.  Testing software for my monkey behaviour, so that it doesn’t break when I do things that I&#8217;m not supposed to do - because I am human. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The developer tuts, &#8220;it&#8217;s your own fault&#8221; he says, &#8220;you broke it with your impatience&#8221;.  And that is why Dan North’s recent blog about Monkey Testing fills me with happiness.  Testing software for my monkey behaviour, so that it doesn’t break when I do things that I&#8217;m not supposed to do &#8211; because I am human. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Agile Runt</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7810</link>
		<dc:creator><![CDATA[Agile Runt]]></dc:creator>
		<pubDate>Tue, 20 Feb 2007 17:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7810</guid>
		<description><![CDATA[Have you checked out OpenSTA and other load test apps?  If I understand the philosophy correctly, I think some percentage of monkey factor is usually baked into these kinds of tests (eg. 83% of users will follow the defined path, while 17% will go off and do something wierd) to give the load testers a more realistic scenario.  Cool stuff, there might be some good ideas in there that can be aped (tee hee!) for acceptance testing.]]></description>
		<content:encoded><![CDATA[<p>Have you checked out OpenSTA and other load test apps?  If I understand the philosophy correctly, I think some percentage of monkey factor is usually baked into these kinds of tests (eg. 83% of users will follow the defined path, while 17% will go off and do something wierd) to give the load testers a more realistic scenario.  Cool stuff, there might be some good ideas in there that can be aped (tee hee!) for acceptance testing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan North</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7809</link>
		<dc:creator><![CDATA[Dan North]]></dc:creator>
		<pubDate>Fri, 16 Feb 2007 22:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7809</guid>
		<description><![CDATA[I agree. The purpose of RMonkey isn&#039;t to replace exploratory testing, it&#039;s to simulate realistic soak testing. The randomness allows you to run a large number of similar-but-different, authentic paths through an application. You would be looking for things like deadlocks or timeouts - things that are difficult to detect without load or soak testing, but where lots of instances of &lt;em&gt;identical&lt;/em&gt; paths might not show up an error.

It&#039;s then up to the testers to determine whether it&#039;s a defect that should be fixed or whether it&#039;s acceptable behaviour and enough of a rarity not to care. So the programmers wouldn&#039;t invest effort unless it was deemed to be worth it. Or something like that anyway - as I said, it was late at night :)]]></description>
		<content:encoded><![CDATA[<p>I agree. The purpose of RMonkey isn&#8217;t to replace exploratory testing, it&#8217;s to simulate realistic soak testing. The randomness allows you to run a large number of similar-but-different, authentic paths through an application. You would be looking for things like deadlocks or timeouts &#8211; things that are difficult to detect without load or soak testing, but where lots of instances of <em>identical</em> paths might not show up an error.</p>
<p>It&#8217;s then up to the testers to determine whether it&#8217;s a defect that should be fixed or whether it&#8217;s acceptable behaviour and enough of a rarity not to care. So the programmers wouldn&#8217;t invest effort unless it was deemed to be worth it. Or something like that anyway &#8211; as I said, it was late at night :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Prashant Gandhi</title>
		<link>http://dannorth.net/2007/02/15/monkey-business-value/#comment-7808</link>
		<dc:creator><![CDATA[Prashant Gandhi]]></dc:creator>
		<pubDate>Fri, 16 Feb 2007 15:58:23 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/2007/02/monkey-business-value#comment-7808</guid>
		<description><![CDATA[Dan,

Testing your code to prevent code entropy and to scope the development task is valuable. Writing tests to replace exploratory testing is not.

Monkey testing would give another excuse for developers to code for functionality which has not really been asked for. Also, isnt it faster to just do the random exploratory testing than writing tests for it ? And if those tests are really important, I would argue that you would need them in your story acceptance criteria as main tests.

Just my $0.02 for what its worth !!

regards,
Prashant]]></description>
		<content:encoded><![CDATA[<p>Dan,</p>
<p>Testing your code to prevent code entropy and to scope the development task is valuable. Writing tests to replace exploratory testing is not.</p>
<p>Monkey testing would give another excuse for developers to code for functionality which has not really been asked for. Also, isnt it faster to just do the random exploratory testing than writing tests for it ? And if those tests are really important, I would argue that you would need them in your story acceptance criteria as main tests.</p>
<p>Just my $0.02 for what its worth !!</p>
<p>regards,<br />
Prashant</p>
]]></content:encoded>
	</item>
</channel>
</rss>

