Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Didnt run into big issues WatiN via xUnit.net myself.</p> <p>Here's a laundry list, which people should feel free to edit into and/or suggest updates to:</p> <ul> <li>Is the NUnit process admin? Is the IE its spawning admin? have a look in Task Manager. (Not that running as admin is a panacea - you ideally want to avoid this, but as a way of eliminating reasons for it not to work)</li> <li>Does running via TestDriven.net, CodeRush or ReSharper help?</li> <li>Have you [referenced the relevant dlls as a way to get] the dependent DLLs such as shdocvvw.dll sitting alongside your test assembly] ?</li> <li>Have you tried seeing if Fiddler shows anything timing out?</li> <li>Have you tried browsing by hand to make sure any security dialogs have been OK'd in the context? e.g., sometimes your test context might be admin whereas your normal browsing profile might not be (depends on browser) - e.g., if you have ignored a cert warning in one context but not the other this might cause an issue.</li> </ul> <p>One big gotcha that bit me wrt WatiN is that after a few thousand invocations on WS08 IE will refuse to cooperate until you log off and on again (see one of my outstanding questions). The route I went down (I needed fail-proof monitoring) was to use the WatiN recorder and then port those to HtmlAgilityPack with LINQ querying with hand-coded GET/POST stuff using WebRequest which works quite well but obviously doesnt handle JavaScript which obviously renders it academic for many scenarios.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload