<?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: Testing Lessons From a Glass Factory</title>
	<atom:link href="http://blog.utest.com/testing-lessons-from-a-glass-factory/2010/07/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.utest.com/testing-lessons-from-a-glass-factory/2010/07/</link>
	<description>Software Testing Community</description>
	<lastBuildDate>Wed, 08 Feb 2012 08:18:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Quality Control Blogger</title>
		<link>http://blog.utest.com/testing-lessons-from-a-glass-factory/2010/07/comment-page-1/#comment-16654</link>
		<dc:creator>Quality Control Blogger</dc:creator>
		<pubDate>Sat, 14 Aug 2010 12:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=7311#comment-16654</guid>
		<description>I agree variety needs to be accounted for in testing especially for web apps that are not for internal use. In my world our network admins control or push out updates to all workstations and the apps I support are internal apps so variety is not a concern however in the past I have worked on projects which were customer facing and the software worked well on one machine but would fail on others due to OS, Browser settings (especially JavaScript setttings!) as well as a variety of other random things. I think it is important to define the scope of testing including these factors in your test plan to make sure you have covered everything the app is supporting</description>
		<content:encoded><![CDATA[<p>I agree variety needs to be accounted for in testing especially for web apps that are not for internal use. In my world our network admins control or push out updates to all workstations and the apps I support are internal apps so variety is not a concern however in the past I have worked on projects which were customer facing and the software worked well on one machine but would fail on others due to OS, Browser settings (especially JavaScript setttings!) as well as a variety of other random things. I think it is important to define the scope of testing including these factors in your test plan to make sure you have covered everything the app is supporting</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stanton Champion</title>
		<link>http://blog.utest.com/testing-lessons-from-a-glass-factory/2010/07/comment-page-1/#comment-16457</link>
		<dc:creator>Stanton Champion</dc:creator>
		<pubDate>Tue, 03 Aug 2010 21:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=7311#comment-16457</guid>
		<description>Carla,

You&#039;re right.  It is checking for variance and deviation in its barest form, but industrial QA as a discipline is about both measuring that deviation and then understanding it.  It&#039;s testing - just a very different kind.</description>
		<content:encoded><![CDATA[<p>Carla,</p>
<p>You&#8217;re right.  It is checking for variance and deviation in its barest form, but industrial QA as a discipline is about both measuring that deviation and then understanding it.  It&#8217;s testing &#8211; just a very different kind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carla, Calgary</title>
		<link>http://blog.utest.com/testing-lessons-from-a-glass-factory/2010/07/comment-page-1/#comment-16456</link>
		<dc:creator>Carla, Calgary</dc:creator>
		<pubDate>Tue, 03 Aug 2010 20:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=7311#comment-16456</guid>
		<description>One might argue that this is checking (looking for devation, variances) versus testing.</description>
		<content:encoded><![CDATA[<p>One might argue that this is checking (looking for devation, variances) versus testing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

