Using WatiN through MbUnit to test ASP .Net MVC web application

Answer 1

There should be no significant differences testing a website on locahost.

Two possible causes:

1. If your webpage contains any significant AJAX then it's possible that the page never appears to be fully loaded so WatiN just keeps waiting.

2. I have fixed one or two bugs in WatiN now and then related to detecting that a page has been fully loaded. You might try grabbing the WatiN trunk source and building a fresh copy of the latest code.

If none of that helps, WatiN also has "NoWait" variants of several actions like clicking. You can also override what it means to WatiN to wait for a page to be complete by registering a WaitForComplete handler.

Answer 2

I've had this happen to me when I had a reference to a resource that didn't load.

• Do have a reference to a JS, CSS, or image file that doesn't exist?
• If you look at the HTTP traffic with Fiddler do you see any connections timing out?

Answer 3

Make sure the program is running as an administrator. On Win7 it will load the page but Watin can't access the DOM unless Visual Studio or Gallio Icarus are started with administrator privileges.