I've recently done work at a company where there are no automated tests, and tests aren't part of the culture. I've been writing tests for so long now that it's jarring to consider working without them, so I've gone ahead and written tests for my part of the work. As I've done so it's really brought home the advantages of writing tests, and I wanted to list them out.

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/dcD

WatiN lets you attach to browser windows so you can verify their contents and close them as part of your tests, but the standard API doesn't detect windows with PDF documents in them. Here's an extension method which does.

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/dTO

WatiN's DomContainer.WaitForComplete() method pauses test execution until the DOM has finished loading, but if your page has functions registered with JQuery's ready() function, you'll probably want to wait for those to finish executing before testing it. Here's a WatiN extension method which pauses test execution until that happens.

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/dNt

I've been doing a fair amount of UI testing using WatiN recently – here’s some extension methods I've found useful.

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/dIn