ASP.net Teamhttp://weblogs.asp.net/joberg/atom.aspxCommunity Server2005-04-19T17:17:00Zhttp://weblogs.asp.net/joberg/archive/2005/05/02/405286.aspx2005-05-02T17:10:00Z2005-05-02T17:10:00Z<font face="Arial">In this article, I’ll describe some techniques to wrap an Internet Explorer window in order to facilitate the automation for verifying the behavior of web applications. Unit testing can be a great help to maintain the functionality of each specific blocks of code; however, as the application concretize itself, it is also important to consider the automation of a few sets of end user scenarios to make sure that your application doesn’t break over time. (</font><A href="http://weblogs.asp.net/joberg/articles/405283.aspx"><font face="Arial">more...</font></a><font face="Arial">)</font><img src="http://weblogs.asp.net/aggbug.aspx?PostID=405286" width="1" height="1">JoBerghttp://weblogs.asp.net/members/JoBerg.aspxhttp://weblogs.asp.net/joberg/archive/2005/04/19/403397.aspx2005-04-19T21:17:00Z2005-04-19T21:17:00Z<p><font face="Arial">The platform invocation (“P/invoke”) framework was designed to allow interaction between your .net application and unmanaged DLL functions. When it comes to UI automation, that framework is very useful since it is rare that any given product provides a built-in automation system. In the following article, I’ll explain different techniques to automate a user interface by using the functionalities of the operating system beneath it. (<A href="http://weblogs.asp.net/joberg/articles/403396.aspx">more...</a>)</font></p><img src="http://weblogs.asp.net/aggbug.aspx?PostID=403397" width="1" height="1">JoBerghttp://weblogs.asp.net/members/JoBerg.aspx