<?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: John Henry, Manual Tester</title>
	<atom:link href="http://tynerblain.com/blog/2006/08/17/manual-tester/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/08/17/manual-tester/</link>
	<description>Software product success.</description>
	<lastBuildDate>Thu, 18 Mar 2010 20:39:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/08/17/manual-tester/comment-page-1/#comment-470362</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Thu, 01 Jan 2009 17:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/08/17/manual-tester/#comment-470362</guid>
		<description>Shrini, thanks for the insights!  For the &quot;it must be quantified&quot; crowd, there are a couple options.  One is to aggregate feedback through a survey (4 out of 5 users found this to be confusing) or (10 users were surveyed, and rated this page a 2.4 on a scale of 1 to 7 for usability).  Another approach is to apply a heuristic analysis, and quantify the results (this workflow scored a 7 out of 20 for &#039;usability best practices&#039;).</description>
		<content:encoded><![CDATA[<p>Shrini, thanks for the insights!  For the &#8220;it must be quantified&#8221; crowd, there are a couple options.  One is to aggregate feedback through a survey (4 out of 5 users found this to be confusing) or (10 users were surveyed, and rated this page a 2.4 on a scale of 1 to 7 for usability).  Another approach is to apply a heuristic analysis, and quantify the results (this workflow scored a 7 out of 20 for &#8216;usability best practices&#8217;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shrini Kulkarni</title>
		<link>http://tynerblain.com/blog/2006/08/17/manual-tester/comment-page-1/#comment-470361</link>
		<dc:creator>shrini Kulkarni</dc:creator>
		<pubDate>Thu, 01 Jan 2009 17:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/08/17/manual-tester/#comment-470361</guid>
		<description>&gt;&gt;&gt;We can use manual testing to provide us with the kinds of feedback that can’t be automated. Things like “This UI is confusing” and “Why won’t it let me…?”

In otherwords, testers (human, sapient) provide &quot;qualitative&quot; feedback, information that stakeholders care about - Pay attention that &quot;qualitative feedback ...

Well, those who swear by &quot;quantification&quot; and metrics ... would not respect these qualitative feedback... just like American automotive manufacturers.
According to them &quot;anything that is not quantified, measured, can not be improved&quot; ....

What a pity ... this affects whole software community ...

Shrini</description>
		<content:encoded><![CDATA[<p>&gt;&gt;&gt;We can use manual testing to provide us with the kinds of feedback that can’t be automated. Things like “This UI is confusing” and “Why won’t it let me…?”</p>
<p>In otherwords, testers (human, sapient) provide &#8220;qualitative&#8221; feedback, information that stakeholders care about &#8211; Pay attention that &#8220;qualitative feedback &#8230;</p>
<p>Well, those who swear by &#8220;quantification&#8221; and metrics &#8230; would not respect these qualitative feedback&#8230; just like American automotive manufacturers.<br />
According to them &#8220;anything that is not quantified, measured, can not be improved&#8221; &#8230;.</p>
<p>What a pity &#8230; this affects whole software community &#8230;</p>
<p>Shrini</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/08/17/manual-tester/comment-page-1/#comment-54703</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Sat, 19 Aug 2006 04:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/08/17/manual-tester/#comment-54703</guid>
		<description>Thanks, Roger!</description>
		<content:encoded><![CDATA[<p>Thanks, Roger!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger L. Cauvin</title>
		<link>http://tynerblain.com/blog/2006/08/17/manual-tester/comment-page-1/#comment-54702</link>
		<dc:creator>Roger L. Cauvin</dc:creator>
		<pubDate>Fri, 18 Aug 2006 23:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/08/17/manual-tester/#comment-54702</guid>
		<description>Scott, I really liked this entry, because it ties together the issue of requirements vs. design and the issue of testability in principle vs. testability in practice.  I just blogged about it &lt;a href=&quot;http://cauvin.blogspot.com/2006/08/specifications-and-manual-tests.html&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Scott, I really liked this entry, because it ties together the issue of requirements vs. design and the issue of testability in principle vs. testability in practice.  I just blogged about it <a href="http://cauvin.blogspot.com/2006/08/specifications-and-manual-tests.html" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
