Question

我的团队拥有一支由我们的团队服务器自动操作的WatiN测试套。我们最近把我们的所有建筑代理人都转至64个轨道,我也把我们的WatiN测试改用X64模式的UNnit。由于Interop呼吁失败,或出于其他原因,Watin总是给我们造成无法正常的测试失败,但总是非常少见。由于把所有东西都转至64轨道,我们几乎所有的试验套案都因下列例外情况而失效:

Test(s) failed. System.InvalidCastException : Specified cast is not valid.
    at SHDocVw.IWebBrowser2.get_HWND()
    at WatiN.Core.Native.InternetExplorer.IEBrowser.get_hWnd()
    at WatiN.Core.DomContainer.StartDialogWatcher()
    at WatiN.Core.IE.CreateNewIEAndGoToUri(Uri uri, IDialogHandler logonDialogHandler, Boolean createInNewProcess)
    ...

I found a 。在WatiN用户看到同样的例外,但这是因为她正在尝试多读。我们没有做任何这样的事情,我们没有像WatiN文件所建议的那样,使用正确的国家公寓。我确实注意到这个问题,但有人评论说这可能是因为x86诉x64模式。

我如何避免造成我检测经常失败的错误?

如果只是转而采用32个轨道模式,我可以处理此事,但我很想知道,没有更好的解决办法。感谢。

UPDATE:
After leaving the jobs as using 64 bit NUnit runner for about 5+ runs of the test suites, they failed every time except once with this same error. We switched them back to 32 bit and have had 10+ successful runs since. I guess the temporary fix for now is use a 32 bit NUnit runner although I am still looking for a reason this happens or a solution that would allows us to switch back to x64.

Answer 1

I am using Watin on x64 and it caused me some troubles. I recently reviewed the source code of Watin and it seems the PInvoke calls are flawed (working only on 32b system correctly). If you execute certain methods they overwrite some parts of memory (as 32b is reserved for 64b result) thus making strange errors.

This is just an example one: WatiN-2.1.0.1196/source/src/Core/Native/Windows/Win32.cs

public static extern Int32 SendMessageTimeout(IntPtr hWnd, Int32 msg, Int32 wParam, Int32 lParam, Int32 fuFlags, Int32 uTimeout, ref Int32 lpdwResult);

VS 更正

public static extern IntPtr SendMessageTimeout(IntPtr hWnd, uint msg, UIntPtr wParam, IntPtr lParam, uint fuFlags, uint uTimeout, out IntPtr lResult);

For full change check http://pastebin.com/KaVpM6wT It needs a rebuild of the Watin.Core dll of course and comes with no warranty.

友情链接