woensdag 11 februari 2009

Released WatiN 2.0 CTP3

I'm happy to announce the third CTP release of WatiN 2.0, offering support for both Internet Explorer and FireFox.

Changes in this release

  • Implemented support on Mozilla.Frame to get access to elements inside the document of a Frame.
  • Implemented support on Mozilla.Frame to get access to elements inside the document of an IFrame.
  • Implemented Eval on Mozilla.Document (= FireFox and Frame) and added to the IFrame interface

Fixed bugs

  • Form.Submit didn't wait for a possible postback and page load.

Enjoy testing with WatiN!

Tags van Technorati:

4 reacties:

Bruno zei

Any idea when WatiN 2.0 will be final?

Thanks!

Jeroen zei

Hi Bruno,

I expect to publish the first beta this month. Why still beta? because the internal architecture has changed a lot compared to the CTP and 1.3 releases. So I think its good to give it some time to mature.

HTH,
Jeroen

Robert zei

How do I detect active instances of existing browsers and obtain access to their DOM?

I am trying to use WatiN to identify open browsers that are running my app and refresh them from a windows app; How do I go about doing that for Firefox. I have it working for IE

Hertzel Karbasi zei

Hello
Your assistance to following issue would be much appreciated:
We have managed to run WATIN (all versions) on XP. But it fails on Win2003+IE8 with following exception on new WatiN.Core.IE():

An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in mscorlib.dll
Additional information: Interface not registered (Exception from HRESULT: 0x80040155)

Best Regards
Hertzel


at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode)
at WatiN.Core.Native.InternetExplorer.IEUtils.EnumIWebBrowser2Interfaces(IWebBrowser2Processor processor)
at WatiN.Core.Native.InternetExplorer.FrameCountProcessor.GetFrameCountFromHTMLDocument(HTMLDocument htmlDocument)
at WatiN.Core.Native.InternetExplorer.IEWaitForComplete.WaitForFramesToComplete(IHTMLDocument2 maindocument)
at WatiN.Core.Native.InternetExplorer.IEWaitForComplete.WaitForCompleteOrTimeout()
at WatiN.Core.WaitForCompleteBase.DoWait()
at WatiN.Core.DomContainer.WaitForComplete(IWait waitForComplete)
at WatiN.Core.IE.WaitForComplete(Int32 waitForCompleteTimeOut)
at WatiN.Core.DomContainer.WaitForComplete()
at WatiN.Core.Browser.GoTo(Uri url)
at WatiN.Core.IE.FinishInitialization(Uri uri)
at WatiN.Core.IE.CreateNewIEAndGoToUri(Uri uri, IDialogHandler logonDialogHandler, Boolean createInNewProcess)
at WatiN.Core.IE..ctor(String url, Boolean createInNewProcess)\r\n at ConsoleApplication1.Program.test()
in C:\\Documents and Settings\\optinity\\My Documents\\Visual Studio 2005\\Projects\\test\\ConsoleApplication1\\ConsoleApplication1\\Program.cs:line 43
at ConsoleApplication1.Program.Main(String[] args) in C:\\Documents and Settings\\optinity\\My Documents\\Visual Studio 2005\\Projects\\test\\ConsoleApplication1\\ConsoleApplication1\\Program.cs:line 19
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()"