<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>UI Unit Testing with WatiN - Part #1 - Introduction</title><link>http://weblogs.asp.net/alnurismail/archive/2008/12/12/ui-unit-testing-with-watin-part-1-introduction.aspx</link><description>There is an arsenal of tools readily available for unit testing web applications. Unit testing both the data access and business logic tiers is a common best practice and a requirement for developing complex web applications. Solutions typically contain</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>UI Unit Testing with WatiN - Part #2 – Tips &amp; Tricks</title><link>http://weblogs.asp.net/alnurismail/archive/2008/12/12/ui-unit-testing-with-watin-part-1-introduction.aspx#6946200</link><pubDate>Sun, 08 Mar 2009 05:25:55 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6946200</guid><dc:creator>A.I on the 1s and 0s</dc:creator><author>A.I on the 1s and 0s</author><description>&lt;p&gt;In my first post about WatiN I introduced the open source API, and provided a simple demo to give a taste&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6946200" width="1" height="1"&gt;</description></item><item><title>re: UI Unit Testing with WatiN - Part #1 - Introduction</title><link>http://weblogs.asp.net/alnurismail/archive/2008/12/12/ui-unit-testing-with-watin-part-1-introduction.aspx#6924365</link><pubDate>Mon, 23 Feb 2009 20:05:47 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6924365</guid><dc:creator>Nathan</dc:creator><author>Nathan</author><description>&lt;p&gt;I created 10 unit tests (MSTEST) utilizing the Watin.Core.dll. My tests run in about 10 seconds when running using Visual Studio. We have a project that is using reflection to automatically run our test project assembly via a web service. The web service then returns the results of the unit tests to a web page. The plan is to run the tests for each of our 50 production servers to verify the web site on each server if functioning as it should. When running the tests using reflection in the web service the tests take approximately 3 minutes to complete. Do you have any idea why there would be such a difference in the amount of time it takes for the tests to complete?&lt;/p&gt;
&lt;p&gt;Any feedback is appreciated&lt;/p&gt;
&lt;p&gt;Nathan&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6924365" width="1" height="1"&gt;</description></item><item><title>re: UI Unit Testing with WatiN - Part #1 - Introduction</title><link>http://weblogs.asp.net/alnurismail/archive/2008/12/12/ui-unit-testing-with-watin-part-1-introduction.aspx#6781157</link><pubDate>Sat, 13 Dec 2008 06:29:22 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6781157</guid><dc:creator>Kambiz</dc:creator><author>Kambiz</author><description>&lt;p&gt;Fantastic is just a little word for this!&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6781157" width="1" height="1"&gt;</description></item></channel></rss>