<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>RoutineBot - GUI Test Automation Robot &#187; Uncategorized</title>
	<atom:link href="http://www.routinebot.com/category/uncategorized/feed" rel="self" type="application/rss+xml" />
	<link>http://www.routinebot.com</link>
	<description>Automate software GUI testing within Agile software testing process as well as any other routine task</description>
	<lastBuildDate>Mon, 22 Aug 2011 19:46:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How do I keep track of unexpected UI bugs during GUI Automation Load Tests?</title>
		<link>http://www.routinebot.com/how-do-i-keep-track-of-unexpected-ui-bugs-during-gui-automation-load-tests.htm</link>
		<comments>http://www.routinebot.com/how-do-i-keep-track-of-unexpected-ui-bugs-during-gui-automation-load-tests.htm#comments</comments>
		<pubDate>Wed, 08 Dec 2010 08:34:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[conducting GUI Automation Load Tests]]></category>
		<category><![CDATA[GUI test cases]]></category>
		<category><![CDATA[recording of automated GUI test cases]]></category>
		<category><![CDATA[unexpected UI bugs]]></category>

		<guid isPermaLink="false">http://www.routinebot.com/?p=567</guid>
		<description><![CDATA[





GUI Test Automation &#8211; How-To Tips!
Download How-To Tips Now!





// 





While conducting GUI Automation Load Tests is a must in order to identify any unexpected UI bugs and crashes under varying loads, keeping track of such issues is far from easy. The inherent nature of load tests (high traffic and quick execution speed) makes it a [...]]]></description>
		<wfw:commentRss>http://www.routinebot.com/how-do-i-keep-track-of-unexpected-ui-bugs-during-gui-automation-load-tests.htm/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Unit restriction in RoutineBot 2.0</title>
		<link>http://www.routinebot.com/unit-restriction-in-routinebot-2-0.htm</link>
		<comments>http://www.routinebot.com/unit-restriction-in-routinebot-2-0.htm#comments</comments>
		<pubDate>Mon, 27 Jul 2009 16:46:27 +0000</pubDate>
		<dc:creator>Developer</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.routinebot.com/?p=400</guid>
		<description><![CDATA[As RoutineBot uses FastScript as script engine, there are 2 restrictions:
1.  If you use units in you project, you must use quoted names in uses-decalartion.
E.g.  in PascalScript these syntax is invalid:
uses unit1;
instead use syntax
uses 'unit1';
2. Unit structure must be same as default script. E.g. in pure Pascal structure of unit is
Unit unitname;
interface
function, procedures,constant and other [...]]]></description>
		<wfw:commentRss>http://www.routinebot.com/unit-restriction-in-routinebot-2-0.htm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

