title: WatiN best practices/rules of thumb for an ASP.NET MVC app
body: <p>I'm an avid TDD and BDD fan but haven't done much in the ways of UI testing. I have an ASP.NET MVC 3 application with many MSpec tests and I'd like to add presentation tests using WatiN.</p>
  
  <p>What sort of stuff do you test? Do I have to write tests for the initial load of the UI or only for things that changed due to user interaction?</p>
  
  <p>What are, in short, good rules of thumb and best practices when writing WatiN (and UI tests in general) tests?</p>