<?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: developer testing vs. tester testing</title>
	<atom:link href="http://www.etagwerker.com/2009/04/developer-testing-vs-tester-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.etagwerker.com/2009/04/developer-testing-vs-tester-testing/</link>
	<description>Ernesto Tagwerker writes about technology</description>
	<lastBuildDate>Tue, 31 Jan 2012 14:07:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: etagwerker</title>
		<link>http://www.etagwerker.com/2009/04/developer-testing-vs-tester-testing/comment-page-1/#comment-24045</link>
		<dc:creator>etagwerker</dc:creator>
		<pubDate>Mon, 11 Oct 2010 15:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://etagwerker.wordpress.com/?p=141#comment-24045</guid>
		<description>I cannot assert that a tester cannot be a good developer. That could happen. But it will depend on the person and the education of that person. 

A developer can be a good tester. But most of the time, the person who builds the code is worse at testing the code than someone who doesn&#039;t build the code.</description>
		<content:encoded><![CDATA[<p>I cannot assert that a tester cannot be a good developer. That could happen. But it will depend on the person and the education of that person. </p>
<p>A developer can be a good tester. But most of the time, the person who builds the code is worse at testing the code than someone who doesn&#8217;t build the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shakti</title>
		<link>http://www.etagwerker.com/2009/04/developer-testing-vs-tester-testing/comment-page-1/#comment-24042</link>
		<dc:creator>Shakti</dc:creator>
		<pubDate>Fri, 08 Oct 2010 09:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://etagwerker.wordpress.com/?p=141#comment-24042</guid>
		<description>You said a software developer can be a tester, but I must say software tester cant be a good software developer. There is no comparison between software tester and developer. Software Tester are nothing before software developer. A developer uses whole of the mind, techniques, effort to write a piece of code to develop a software or application, and what a tester does, just test that and find bugs, if this work is assigned to another developer, he can easily do testing because a developer can be a good tester, but a tester cant be a good developer.</description>
		<content:encoded><![CDATA[<p>You said a software developer can be a tester, but I must say software tester cant be a good software developer. There is no comparison between software tester and developer. Software Tester are nothing before software developer. A developer uses whole of the mind, techniques, effort to write a piece of code to develop a software or application, and what a tester does, just test that and find bugs, if this work is assigned to another developer, he can easily do testing because a developer can be a good tester, but a tester cant be a good developer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: etagwerker</title>
		<link>http://www.etagwerker.com/2009/04/developer-testing-vs-tester-testing/comment-page-1/#comment-226</link>
		<dc:creator>etagwerker</dc:creator>
		<pubDate>Wed, 02 Dec 2009 17:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://etagwerker.wordpress.com/?p=141#comment-226</guid>
		<description>Thanks!

A good testing phase is always necessary in order to engineer high-quality solutions and avoid client complaints. 

Also, a clearly define set of features is necessary for testing to know what is expected.  These features should be reviewed, understood and approved by the client.</description>
		<content:encoded><![CDATA[<p>Thanks!</p>
<p>A good testing phase is always necessary in order to engineer high-quality solutions and avoid client complaints. </p>
<p>Also, a clearly define set of features is necessary for testing to know what is expected.  These features should be reviewed, understood and approved by the client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcelo Galarza</title>
		<link>http://www.etagwerker.com/2009/04/developer-testing-vs-tester-testing/comment-page-1/#comment-217</link>
		<dc:creator>Marcelo Galarza</dc:creator>
		<pubDate>Tue, 01 Dec 2009 14:06:28 +0000</pubDate>
		<guid isPermaLink="false">http://etagwerker.wordpress.com/?p=141#comment-217</guid>
		<description>Pretty awesome article. Short as Effective. I totally agree with you, I would add it&#039;s essencial in a project to focus forces in each other&#039;s roles, and there is where the developers must  rely on tester to do what they can do best, seek and break down system features.
Quality assurance must  never be underestimated if we want avoid our clients rejections ;).</description>
		<content:encoded><![CDATA[<p>Pretty awesome article. Short as Effective. I totally agree with you, I would add it&#8217;s essencial in a project to focus forces in each other&#8217;s roles, and there is where the developers must  rely on tester to do what they can do best, seek and break down system features.<br />
Quality assurance must  never be underestimated if we want avoid our clients rejections <img src='http://www.etagwerker.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
</channel>
</rss>

