http://msmvps.com/blogs/omar/archive/2008/10/27/how-to-convince-developers-and-management-to-use-automated-unit-test-for-ajax-websites.aspxEveryone agrees that unit testing is a good thing, we should all write unit tests. We read articles and blogs to keep us up-to-date on what’s going on in the unit test world so that we can sound cool talking to peers at lunch. But when we really sit downenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/omar/archive/2008/10/27/how-to-convince-developers-and-management-to-use-automated-unit-test-for-ajax-websites.aspx#1731756Mon, 12 Oct 2009 01:06:20 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1731756PimpThisBlog.com<p>Thank you for submitting this cool story - Trackback from PimpThisBlog.com</p> <img src="http://msmvps.com/aggbug.aspx?PostID=1731756" width="1" height="1">http://msmvps.com/blogs/omar/archive/2008/10/27/how-to-convince-developers-and-management-to-use-automated-unit-test-for-ajax-websites.aspx#1652220Tue, 28 Oct 2008 10:07:08 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1652220Ashraful Alam<p>Omar,</p> <p>WatiN is good framework, however it that limited support on multi-browser support, as well as lacking for advanced java-script functionalities. There is another tool named: &quot;WebAii&quot;, which has richer support for multi-browser as well as client side scripting (even for silverlight component). The problem with WebAii is it requires separate software installed on developers machine, where as for WatiN, it doesn’t require to install any additional software; besides, WatiN is an open source project. However I see both has some pros and cons, but personally I like to use WatiN for most cases and use WebAii for the tests that requires to check advanced client side and multi-browser functionalities.</p> <p>It would be really great if we have a post from you with respect to comparing both frameworks from your experienced view!</p> <p>Thanks.</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1652220" width="1" height="1">http://msmvps.com/blogs/omar/archive/2008/10/27/how-to-convince-developers-and-management-to-use-automated-unit-test-for-ajax-websites.aspx#1652129Mon, 27 Oct 2008 16:29:16 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1652129omar<p>Greg, you are right about unit tests. In our case, we decided to choose each web service as a unit. If a test breaks, we know which webservice has broken. It was just too expensive to get into more granular level than web methods.</p> <p>We are using WatiN and it works wonders for us. </p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1652129" width="1" height="1">http://msmvps.com/blogs/omar/archive/2008/10/27/how-to-convince-developers-and-management-to-use-automated-unit-test-for-ajax-websites.aspx#1652121Mon, 27 Oct 2008 15:42:55 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1652121Greg<p>Good post, but it sounds like you&#39;re misusing the term &quot;unit test.&quot; Writing tests that exercise all your tiers programatically are integration tests. The &quot;unit&quot; in unit test means that the impact of changes is isolated to a single unit, that is, if and only if you change the unit (a class usually) can that test break. </p> <p>BTW Selenium and Watir solved the whole web UI testing thing for years now.</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1652121" width="1" height="1">