<?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: UI Automation Out of Control</title>
	<atom:link href="http://www.testingmentor.com/imtesty/2009/11/18/ui-automation-out-of-control/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.testingmentor.com/imtesty/2009/11/18/ui-automation-out-of-control/</link>
	<description>Treatises on the practice of software testing</description>
	<lastBuildDate>Tue, 07 Feb 2012 09:15:11 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: testingmentor</title>
		<link>http://www.testingmentor.com/imtesty/2009/11/18/ui-automation-out-of-control/comment-page-1/#comment-309</link>
		<dc:creator>testingmentor</dc:creator>
		<pubDate>Thu, 19 Nov 2009 05:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://testingmentor.com/imtesty/2009/11/18/ui-automation-out-of-control/#comment-309</guid>
		<description>Thanks Wesley. These are some great examples of things that could cause problems with visual comparison in automation.

There is some interesting work being done with visual comparison such as histograms, color and pixel tolerance maps, etc. 

This is all interesting work, but the simple fact is that sometimes it is easier, more reliable, and cheaper to validate UI visuals via usability testing, end-to-end or user scenario testing, exploratory testing, dog-fooding, self-hosting, beta feedback, etc.

Many of us have been down that hard way path...but sometimes the school of hard knocks provides the best education. 

Thursday, August 13, 2009 1:52 AM by I.M.Testy</description>
		<content:encoded><![CDATA[<p>Thanks Wesley. These are some great examples of things that could cause problems with visual comparison in automation.</p>
<p>There is some interesting work being done with visual comparison such as histograms, color and pixel tolerance maps, etc. </p>
<p>This is all interesting work, but the simple fact is that sometimes it is easier, more reliable, and cheaper to validate UI visuals via usability testing, end-to-end or user scenario testing, exploratory testing, dog-fooding, self-hosting, beta feedback, etc.</p>
<p>Many of us have been down that hard way path&#8230;but sometimes the school of hard knocks provides the best education. </p>
<p>Thursday, August 13, 2009 1:52 AM by I.M.Testy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WesleyB77</title>
		<link>http://www.testingmentor.com/imtesty/2009/11/18/ui-automation-out-of-control/comment-page-1/#comment-308</link>
		<dc:creator>WesleyB77</dc:creator>
		<pubDate>Thu, 19 Nov 2009 05:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://testingmentor.com/imtesty/2009/11/18/ui-automation-out-of-control/#comment-308</guid>
		<description>I couldn’t agree with you more. 

We had tests in a previous team of mine that tested parts of MSTIME (Microsoft Timed Interactive Multimedia Extensions) by comparing a known good screenshot to a screenshot taken using the binary being tested. I arrived a few years after the code was written, and the nightmare was not over. There were a lot of problems. Due to the sheer magnitude of environments and platforms and machines being tested, there were always a high number of false positives. 

Sometimes certain video cards on the machine would colour a pixel differently (FAIL), or a frame would be skipped (FAIL), or it would render slowly (FAIL), or ClearType was enabled on the machine (FAIL), or (FAIL) or (FAIL) or (FAIL) or (FAIL). 

It was very frustrating. At the very least though, I learned the hard way that automating everything does not solve all your problems. 

Wednesday, August 12, 2009 1:36 PM by WesleyB77</description>
		<content:encoded><![CDATA[<p>I couldn’t agree with you more. </p>
<p>We had tests in a previous team of mine that tested parts of MSTIME (Microsoft Timed Interactive Multimedia Extensions) by comparing a known good screenshot to a screenshot taken using the binary being tested. I arrived a few years after the code was written, and the nightmare was not over. There were a lot of problems. Due to the sheer magnitude of environments and platforms and machines being tested, there were always a high number of false positives. </p>
<p>Sometimes certain video cards on the machine would colour a pixel differently (FAIL), or a frame would be skipped (FAIL), or it would render slowly (FAIL), or ClearType was enabled on the machine (FAIL), or (FAIL) or (FAIL) or (FAIL) or (FAIL). </p>
<p>It was very frustrating. At the very least though, I learned the hard way that automating everything does not solve all your problems. </p>
<p>Wednesday, August 12, 2009 1:36 PM by WesleyB77</p>
]]></content:encoded>
	</item>
</channel>
</rss>

