<?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: What&#8217;s so special about software testing?</title>
	<atom:link href="http://thetesteye.com/blog/2009/09/whats-so-special-about-software-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://thetesteye.com/blog/2009/09/whats-so-special-about-software-testing/</link>
	<description>by rikard edgren, henrik emilsson and martin jansson - with torbjörn ryber and henrik andersson</description>
	<lastBuildDate>Thu, 17 May 2012 16:53:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rikard Edgren</title>
		<link>http://thetesteye.com/blog/2009/09/whats-so-special-about-software-testing/comment-page-1/#comment-557</link>
		<dc:creator>Rikard Edgren</dc:creator>
		<pubDate>Wed, 15 Sep 2010 18:35:56 +0000</pubDate>
		<guid isPermaLink="false">http://thetesteye.com/blog/?p=480#comment-557</guid>
		<description>unique:
* everyday serendipity
* creates problems instead of solving them (or: solves problems by creating them)

special:
* need to have many active things going on simultaneously
* responsibility/expectations can differ very much</description>
		<content:encoded><![CDATA[<p>unique:<br />
* everyday serendipity<br />
* creates problems instead of solving them (or: solves problems by creating them)</p>
<p>special:<br />
* need to have many active things going on simultaneously<br />
* responsibility/expectations can differ very much</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Did Beatles use Kanban? &#124; thoughts from the test eye</title>
		<link>http://thetesteye.com/blog/2009/09/whats-so-special-about-software-testing/comment-page-1/#comment-432</link>
		<dc:creator>Did Beatles use Kanban? &#124; thoughts from the test eye</dc:creator>
		<pubDate>Wed, 05 May 2010 10:04:30 +0000</pubDate>
		<guid isPermaLink="false">http://thetesteye.com/blog/?p=480#comment-432</guid>
		<description>[...] and put on software testing as a best practice, or something really good. Software testing is unique, and you might violate important aspects when applying a template that doesn&#8217;t match. It is a [...]</description>
		<content:encoded><![CDATA[<p>[...] and put on software testing as a best practice, or something really good. Software testing is unique, and you might violate important aspects when applying a template that doesn&#8217;t match. It is a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rikard Edgren</title>
		<link>http://thetesteye.com/blog/2009/09/whats-so-special-about-software-testing/comment-page-1/#comment-192</link>
		<dc:creator>Rikard Edgren</dc:creator>
		<pubDate>Wed, 07 Oct 2009 06:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://thetesteye.com/blog/?p=480#comment-192</guid>
		<description>I like the Google Translation of the above comment:

&quot;Break, crush and tear apart - that is life, this is happiness.&quot; The unique characteristics of the profession tester.</description>
		<content:encoded><![CDATA[<p>I like the Google Translation of the above comment:</p>
<p>&#8220;Break, crush and tear apart &#8211; that is life, this is happiness.&#8221; The unique characteristics of the profession tester.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenQuality.ru &#124; Сентябрьская лента: лучшее за месяц</title>
		<link>http://thetesteye.com/blog/2009/09/whats-so-special-about-software-testing/comment-page-1/#comment-191</link>
		<dc:creator>OpenQuality.ru &#124; Сентябрьская лента: лучшее за месяц</dc:creator>
		<pubDate>Wed, 30 Sep 2009 20:49:38 +0000</pubDate>
		<guid isPermaLink="false">http://thetesteye.com/blog/?p=480#comment-191</guid>
		<description>[...] &#8226;&#160;&#8221;Ломать, крушить и рвать на части &#8211; вот это жизнь, вот это счастье&#8221;. Уникальные характеристики профессии тестировщика. [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8226;&nbsp;&#8221;Ломать, крушить и рвать на части &#8211; вот это жизнь, вот это счастье&#8221;. Уникальные характеристики профессии тестировщика. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Jansson</title>
		<link>http://thetesteye.com/blog/2009/09/whats-so-special-about-software-testing/comment-page-1/#comment-177</link>
		<dc:creator>Martin Jansson</dc:creator>
		<pubDate>Wed, 09 Sep 2009 16:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://thetesteye.com/blog/?p=480#comment-177</guid>
		<description>Regarding &quot;You might say that none of the above is true for an executor of detailed test cases&quot;, there are some who are stuck in a situation where they do not experience any of the good things (at least as I see it).

Creativity is frowned upon if it does not show progress in the current list of test cases to be run.

The idea of never being done is not true if you are done when the assigned test cases in the test matrix are finished. Going outside the already planned test cases is a nono.

Doing things the wrong way is not something the customer would do. Oh really?

Why do you want to destroy? QA/Test team are always so negative.

In a situation like the above I&#039;ve noticed that many try to escape the testing part, to do other test related things such as test planning, writing new test cases etc. Is this dystopia really what many teach and want us to practise? Each time I enter this situation I long for the exploratory way.</description>
		<content:encoded><![CDATA[<p>Regarding &#8220;You might say that none of the above is true for an executor of detailed test cases&#8221;, there are some who are stuck in a situation where they do not experience any of the good things (at least as I see it).</p>
<p>Creativity is frowned upon if it does not show progress in the current list of test cases to be run.</p>
<p>The idea of never being done is not true if you are done when the assigned test cases in the test matrix are finished. Going outside the already planned test cases is a nono.</p>
<p>Doing things the wrong way is not something the customer would do. Oh really?</p>
<p>Why do you want to destroy? QA/Test team are always so negative.</p>
<p>In a situation like the above I&#8217;ve noticed that many try to escape the testing part, to do other test related things such as test planning, writing new test cases etc. Is this dystopia really what many teach and want us to practise? Each time I enter this situation I long for the exploratory way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik Emilsson</title>
		<link>http://thetesteye.com/blog/2009/09/whats-so-special-about-software-testing/comment-page-1/#comment-176</link>
		<dc:creator>Henrik Emilsson</dc:creator>
		<pubDate>Tue, 08 Sep 2009 21:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://thetesteye.com/blog/?p=480#comment-176</guid>
		<description>True, so true...

You also have the possibility to be multidimensionally subjective, which I think is something special for software testing.

Hmm, multidimensional subjectivity is almost unique for software testing, except for certain psychoanalysts in relational psychoanalysis that utilizes it... :-)</description>
		<content:encoded><![CDATA[<p>True, so true&#8230;</p>
<p>You also have the possibility to be multidimensionally subjective, which I think is something special for software testing.</p>
<p>Hmm, multidimensional subjectivity is almost unique for software testing, except for certain psychoanalysts in relational psychoanalysis that utilizes it&#8230; <img src='http://thetesteye.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

