<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: QA Test Automation Requirements (2) &#8211; Usability</title>
	<atom:link href="http://automation-beyond.com/2009/06/07/qa-test-automation-requirements-usability-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://automation-beyond.com/2009/06/07/qa-test-automation-requirements-usability-2/</link>
	<description>An engineering approach to Software Testing and Test Automation</description>
	<lastBuildDate>Fri, 11 May 2012 06:01:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: QA Test Automation Requirements (1) – Usability - Automation Beyond</title>
		<link>http://automation-beyond.com/2009/06/07/qa-test-automation-requirements-usability-2/comment-page-1/#comment-419</link>
		<dc:creator>QA Test Automation Requirements (1) – Usability - Automation Beyond</dc:creator>
		<pubDate>Tue, 26 Jan 2010 21:07:02 +0000</pubDate>
		<guid isPermaLink="false">http://automationbeyond.wordpress.com/?p=106#comment-419</guid>
		<description>[...] Software Quality Assurance Functional/Regression Automated Testing and Test Automation Requirements: Usability, Maintainability, Scalability, and Robustness  [...]</description>
		<content:encoded><![CDATA[<p>[...] Software Quality Assurance Functional/Regression Automated Testing and Test Automation Requirements: Usability, Maintainability, Scalability, and Robustness  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Albert Gareev</title>
		<link>http://automation-beyond.com/2009/06/07/qa-test-automation-requirements-usability-2/comment-page-1/#comment-31</link>
		<dc:creator>Albert Gareev</dc:creator>
		<pubDate>Thu, 26 Nov 2009 14:07:34 +0000</pubDate>
		<guid isPermaLink="false">http://automationbeyond.wordpress.com/?p=106#comment-31</guid>
		<description>Important to mention: usability requirements have universal part and context-specific part.
The article proposed by Disambiguator is about universal requirements to Graphic User Interface.
Testing scripts do not have one.</description>
		<content:encoded><![CDATA[<p>Important to mention: usability requirements have universal part and context-specific part.<br />
The article proposed by Disambiguator is about universal requirements to Graphic User Interface.<br />
Testing scripts do not have one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Disambiguator</title>
		<link>http://automation-beyond.com/2009/06/07/qa-test-automation-requirements-usability-2/comment-page-1/#comment-30</link>
		<dc:creator>Disambiguator</dc:creator>
		<pubDate>Thu, 26 Nov 2009 04:23:10 +0000</pubDate>
		<guid isPermaLink="false">http://automationbeyond.wordpress.com/?p=106#comment-30</guid>
		<description>Good article on usability. Thought your readers might be interested in a list I put together called &quot;Levels of Help.&quot; It&#039;s a treatment of all the various ways we can help users, including many elements that must go in at design time. Here&#039;s the article:
http://dynamicanswers.com/Company/Blog/tabid/54/EntryID/13/Default.aspx</description>
		<content:encoded><![CDATA[<p>Good article on usability. Thought your readers might be interested in a list I put together called &#8220;Levels of Help.&#8221; It&#8217;s a treatment of all the various ways we can help users, including many elements that must go in at design time. Here&#8217;s the article:<br />
<a href="http://dynamicanswers.com/Company/Blog/tabid/54/EntryID/13/Default.aspx" rel="nofollow">http://dynamicanswers.com/Company/Blog/tabid/54/EntryID/13/Default.aspx</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

