<?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: &quot;Don&#8217;t call me a QA!&quot;</title>
	<atom:link href="http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=dont-call-me-a-qa</link>
	<description>A different view of software testing</description>
	<lastBuildDate>Tue, 24 Jan 2012 20:03:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: ColoradoTester</title>
		<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/#comment-1408</link>
		<dc:creator>ColoradoTester</dc:creator>
		<pubDate>Thu, 11 Jun 2009 15:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2009/02/01/dont-call-me-a-qa/#comment-1408</guid>
		<description>Yeah - I find the term QA problematic for several reasons.  Unfortunately, it is embedded in the parlance of clients, organizations, and teams.  Trying to drop the term unilaterally means having to forever explain why you don&#039;t like the term, what it means, what&#039;s a better term, etc. The fact is, most clients show surprisingly little interest in confronting this semantic conundrum.  &quot;We&#039;ve always called it QA.&quot; said one project manager I spoke with, &quot;Hell, I don&#039;t even know what that stands for. Hey, did Jerry bring bagels this morning?&quot;

In addition, there were a few months back in 2005 when some people thought that software &quot;QA&quot; could make a difference by actually looking at development practices and finding ways to make improvements.  When I think back on the dozens of emails, test plans, and other artifacts many of us produced in an effort to pursue this concept of helping &quot;assure quality&quot;, it makes me smile, in a forced, painful way.

How about all those meetings we attended, prepared to unveil some new idea/plan/procedure about improving requirements, traceability, unit testing, or some other aspect of the development process (You remember, the plan you worked on until two in the morning?) only to receive the standard introduction for any idea that originates with testers: &quot;OK, I guess that&#039;s about it. Thanks everybody. Oh...I&#039;m sorry, I guess QA had something they wanted to talk about?&quot;</description>
		<content:encoded><![CDATA[<p>Yeah &#8211; I find the term QA problematic for several reasons.  Unfortunately, it is embedded in the parlance of clients, organizations, and teams.  Trying to drop the term unilaterally means having to forever explain why you don&#8217;t like the term, what it means, what&#8217;s a better term, etc. The fact is, most clients show surprisingly little interest in confronting this semantic conundrum.  &#8220;We&#8217;ve always called it QA.&#8221; said one project manager I spoke with, &#8220;Hell, I don&#8217;t even know what that stands for. Hey, did Jerry bring bagels this morning?&#8221;</p>
<p>In addition, there were a few months back in 2005 when some people thought that software &#8220;QA&#8221; could make a difference by actually looking at development practices and finding ways to make improvements.  When I think back on the dozens of emails, test plans, and other artifacts many of us produced in an effort to pursue this concept of helping &#8220;assure quality&#8221;, it makes me smile, in a forced, painful way.</p>
<p>How about all those meetings we attended, prepared to unveil some new idea/plan/procedure about improving requirements, traceability, unit testing, or some other aspect of the development process (You remember, the plan you worked on until two in the morning?) only to receive the standard introduction for any idea that originates with testers: &#8220;OK, I guess that&#8217;s about it. Thanks everybody. Oh&#8230;I&#8217;m sorry, I guess QA had something they wanted to talk about?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jester tester</title>
		<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/#comment-1350</link>
		<dc:creator>Jester tester</dc:creator>
		<pubDate>Fri, 24 Apr 2009 03:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2009/02/01/dont-call-me-a-qa/#comment-1350</guid>
		<description>Hi, I&#039;m from the Philippines and I work as tester too... I also have the same rant like you regarding Testers being called as QA by other people. But here in our company, we are called testers and there&#039;s no problem but when I encounter other developers and even testers from other companies, when they ask me, &quot;what&#039;s your role in you team?&quot;, I say &quot;Software tester&quot;, then they tell me, &quot;Ahhh, QA!&quot;.

&lt;em&gt;Ahhh, a common variant of Selective hearing. Sadly, as yet I have found no known universal cure.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Hi, I&#8217;m from the Philippines and I work as tester too&#8230; I also have the same rant like you regarding Testers being called as QA by other people. But here in our company, we are called testers and there&#8217;s no problem but when I encounter other developers and even testers from other companies, when they ask me, &#8220;what&#8217;s your role in you team?&#8221;, I say &#8220;Software tester&#8221;, then they tell me, &#8220;Ahhh, QA!&#8221;.</p>
<p><em>Ahhh, a common variant of Selective hearing. Sadly, as yet I have found no known universal cure.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rachel</title>
		<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/#comment-1319</link>
		<dc:creator>Rachel</dc:creator>
		<pubDate>Thu, 26 Feb 2009 11:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2009/02/01/dont-call-me-a-qa/#comment-1319</guid>
		<description>Is the whole world confused by the difference?  Testing and QA are NOT the same.  

Testing is about exercising the system to figure out whether it can be broken too easily, whether it achieves the things the customer wanted and whether it meets the standards set by the company.  

Quality Assurance, is ALL about whether, during the process of producing whatever it is, everyone involved followed the processes and procedures defined properly in order to have confidence that the quality required has been achieved.  

They are different things, utilising different skills (and different people), with the same objective - to ensure a system is produced that achieves the desired level of quality.

Many companies employ neither, a few employ both, I suspect the majority employ testers, but think they have achieved both things by so doing.

&lt;em&gt;Hi Rachel, Thanks for leaving a comment. I suspect the majority employ testers too. &lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Is the whole world confused by the difference?  Testing and QA are NOT the same.  </p>
<p>Testing is about exercising the system to figure out whether it can be broken too easily, whether it achieves the things the customer wanted and whether it meets the standards set by the company.  </p>
<p>Quality Assurance, is ALL about whether, during the process of producing whatever it is, everyone involved followed the processes and procedures defined properly in order to have confidence that the quality required has been achieved.  </p>
<p>They are different things, utilising different skills (and different people), with the same objective &#8211; to ensure a system is produced that achieves the desired level of quality.</p>
<p>Many companies employ neither, a few employ both, I suspect the majority employ testers, but think they have achieved both things by so doing.</p>
<p><em>Hi Rachel, Thanks for leaving a comment. I suspect the majority employ testers too. </em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suzanne</title>
		<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/#comment-1313</link>
		<dc:creator>Suzanne</dc:creator>
		<pubDate>Mon, 23 Feb 2009 19:56:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2009/02/01/dont-call-me-a-qa/#comment-1313</guid>
		<description>I will never call you a QA. To me, QA is taking random samples of service or product to determine an overall measure of standards compliance. It has nothing to do with testing. I would sooner be called a code monkey for all my days than refer to testing as QA. It just doesn&#039;t fit. Even though I am in the minority, I won&#039;t be swayed!

&lt;em&gt;Thanks Suzanne, hopefully others will emulate your sway free stance.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>I will never call you a QA. To me, QA is taking random samples of service or product to determine an overall measure of standards compliance. It has nothing to do with testing. I would sooner be called a code monkey for all my days than refer to testing as QA. It just doesn&#8217;t fit. Even though I am in the minority, I won&#8217;t be swayed!</p>
<p><em>Thanks Suzanne, hopefully others will emulate your sway free stance.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shrini Kulkarni</title>
		<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/#comment-1232</link>
		<dc:creator>shrini Kulkarni</dc:creator>
		<pubDate>Sat, 31 Jan 2009 10:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2009/02/01/dont-call-me-a-qa/#comment-1232</guid>
		<description>I wrote about it, here

http://shrinik.blogspot.com/2006/12/how-can-software-tester-shoot-on.html

Shrini

&lt;em&gt;Thanks for the pointer Shrini.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>I wrote about it, here</p>
<p><a href="http://shrinik.blogspot.com/2006/12/how-can-software-tester-shoot-on.html" rel="nofollow">http://shrinik.blogspot.com/2006/12/how-can-software-tester-shoot-on.html</a></p>
<p>Shrini</p>
<p><em>Thanks for the pointer Shrini.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Kirkham</title>
		<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/#comment-1231</link>
		<dc:creator>Phil Kirkham</dc:creator>
		<pubDate>Sat, 31 Jan 2009 09:22:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2009/02/01/dont-call-me-a-qa/#comment-1231</guid>
		<description>Mouse mats and t-shirts aren&#039;t enough, we have to start getting really evil

I&#039;ll add your rant to the ever growing list...

http://expectedresults.blogspot.com/2008/09/testing-cliches.html

&lt;em&gt;An old rant, but an important one methinks. Now I too can sit in such rarefied company.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Mouse mats and t-shirts aren&#8217;t enough, we have to start getting really evil</p>
<p>I&#8217;ll add your rant to the ever growing list&#8230;</p>
<p><a href="http://expectedresults.blogspot.com/2008/09/testing-cliches.html" rel="nofollow">http://expectedresults.blogspot.com/2008/09/testing-cliches.html</a></p>
<p><em>An old rant, but an important one methinks. Now I too can sit in such rarefied company.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marijane</title>
		<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/#comment-1230</link>
		<dc:creator>marijane</dc:creator>
		<pubDate>Sat, 31 Jan 2009 03:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2009/02/01/dont-call-me-a-qa/#comment-1230</guid>
		<description>I started out as a Software Test Engineer but my official title at my current employer is QA Engineer.  Thankfully, my teammates and I usually refer to ourselves as testers despite the title.

When it comes up, I tell everyone QA stands for &quot;Quality Assessment&quot;, and then they get a diatribe about how it is impossible for a test team to &quot;assure quality&quot;.   If the discussion is happening online, I usually include a link to Elizabeth Hendrickson&#039;s &lt;a href=&quot;http://www.ayeconference.com/you-cant-test-the-wings-back-on-an-airplane/&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;You Can&#039;t Test the Wings Back on an Airplane&lt;/a&gt;.

&lt;em&gt;Thanks for leaving the comment Marijane and the link.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>I started out as a Software Test Engineer but my official title at my current employer is QA Engineer.  Thankfully, my teammates and I usually refer to ourselves as testers despite the title.</p>
<p>When it comes up, I tell everyone QA stands for &#8220;Quality Assessment&#8221;, and then they get a diatribe about how it is impossible for a test team to &#8220;assure quality&#8221;.   If the discussion is happening online, I usually include a link to Elizabeth Hendrickson&#8217;s <a href="http://www.ayeconference.com/you-cant-test-the-wings-back-on-an-airplane/" target="_blank" rel="nofollow">You Can&#8217;t Test the Wings Back on an Airplane</a>.</p>
<p><em>Thanks for leaving the comment Marijane and the link.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: QA or&#8230;? &#171; MGilly&#8217;s QA Blog</title>
		<link>http://www.eviltester.com/index.php/2009/01/30/dont-call-me-a-qa/#comment-1229</link>
		<dc:creator>QA or&#8230;? &#171; MGilly&#8217;s QA Blog</dc:creator>
		<pubDate>Sat, 31 Jan 2009 01:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2009/02/01/dont-call-me-a-qa/#comment-1229</guid>
		<description>[...]  Here is an interesting post on Evil Tester called, &#8220;Don&#8217;t call me a QA!&#8221; Fortuitous, [...]

&lt;em&gt;Mary has crafted some alternative definitions in case you want to change from QA.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>[...]  Here is an interesting post on Evil Tester called, &#8220;Don&#8217;t call me a QA!&#8221; Fortuitous, [...]</p>
<p><em>Mary has crafted some alternative definitions in case you want to change from QA.</em></p>
]]></content:encoded>
	</item>
</channel>
</rss>

