WatiN Woes

I’ve been using WatiN a little bit for some testing on a pet project at the moment and I’ve noticed that between builds – even with no code changes I can get the unit tests that are driving the WatiN framework. It seems to be something to do with the problem that Bruce McLeod describes in this post. However, I am getting the problem on a remote Windows 2003 server running IE 6.0 – the tests are being run as part of a Team Build run.

The wierd thing is that it seems to randomly succeed sometimes. Very strange!


5 thoughts on “WatiN Woes

  1. Jeroen van Menen


    I was surfing the net when I came across your blog. If I can be of any help, please let me know. If you have some exception details, that would be nice.


    Jeroen (main developer of WatiN)

  2. Mitch Denny Post author

    Hi Jeron,

    Thanks for offering to take a look. I’ve sent you an e-mail under seperate cover.

  3. Alex

    Have you seen SWExplorerAutomation (SWEA) (http:\\webunittesting.com). SWEA is very solid and reliable WEB automation product. WATIN uses IE proxy to connect to IE – all calls to IE are marshalled. The approach does not give a testing application full control over browser – frames from different domains, dialogs boxes, capturing browser image, AJAX are serious problem for WATIN. SWEA is based on SOA architecture, which gives more control over IE to support the complex automation features.

  4. Mitch Denny Post author

    Hi Alex,

    Thanks for the suggestion. I’ve actually looked at the product – you mentioned it before.

  5. Bruce McLeod

    Like any automation tool, WatiN is susceptible to timing issues, and if you have a test that is semi-reliable, you may find that this is the issue. On the other hand, you may not care anymore as you posted this a month ago 🙂


    WatiN is not perfect by any means and it has been “alive” for less than a year. The great thing about it is that if it does not support a feature you need, you can simply add it and submit the changes. One thing I live about it is that it is 100% managed code, so all you need to do is checkout and build on a new developers workstation.

    Bruce McLeod

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s