StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWatiN through TFS on Windows 2008 Server
text
Body
copied!<p>I'm trying to run WatiN tests through continuous build on TFS, but I can't get it to work. The errror I get is following:</p> <pre><code>WatiN.Core.Exceptions.IENotFoundException : Could not find an IE window matching constraint: Timeout while waiting to attach to newly created instance of IE.. Search expired after '30' seconds. at WatiN.Core.IE.CreateIEPartiallyInitializedInNewProcess() at WatiN.Core.IE.CreateNewIEAndGoToUri(Uri uri, IDialogHandler logonDialogHandler, Boolean createInNewProcess) at WatiN.Core.IE..ctor(String url, Boolean createInNewProcess) </code></pre> <p>I've read that this may be the cause of</p> <ul> <li>Requests for "localhost" will resolve to the IPv6 address of ::1 by default rather than the IPv4 address of 127.0.0.1 and the WatiN tests will fail.</li> </ul> <p>This is not the case, because I'm testing against a public URL not on the local machine.</p> <ul> <li>IE Enhanced Security Configuration turned on</li> </ul> <p>I've turned this off without any result.</p> <ul> <li>Missing files Microsoft.mshtml.dll, Interop.shdocvw.dll or Watin.Core.dll</li> </ul> <p>Check and double check! I have those in my output directory where the tests are run.</p> <p>The last and final test was to login as the user that runs the build and executes the NUnit testing suite and run the tests by hand.</p> <pre><code>C:\Users\TFSSERVICE>"C:\Program Files\Nunit 2.5.2\bin\net-2.0\nunit-console.exe" /nologo C:\Users\BUILDSERVICE\AppData\Local\Temp\\Continuous\Binaries\Release \\WebTests.dll </code></pre> <p>Guess what! It works executing them manually as the tfs build user. So, what am I missing here? Have any ideas why it just keeps timing out when I run through the msbuild engine?</p> <p>Any thought are welcome! Mikael</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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