I am trying to run the sample test code (here) on a testing machine.
I get the following error - see below.
This computer does not have the testing framework installed on.
I added the relevant WebAii dlls to the application I created so they are included in the bin folder.
What am I missing
Thanks
ee the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ApplicationException: Exception thrown attempting to launch Internet Explorer. Please make sure Internet Explorer is properly installed and you are able to launch it. ---> System.TypeInitializationException: The type initializer for 'ArtOfTest.Common.Win32.Connector' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at ArtOfTest.Common.Win32.Connector..cctor()
--- End of inner exception stack trace ---
at ArtOfTest.Common.Win32.Connector.Start(ConnectorEntryPoint entryPoint, IntPtr windowHandle)
at ArtOfTest.Common.Win32.Connector.Attach(IntPtr& handle, Boolean findTabWindow)
at ArtOfTest.WebAii.BrowserSpecialized.InternetExplorer.InternetExplorerActions.LaunchNewBrowserInstance(Int32 timeout, ProcessWindowStyle windowStyle, String pipename)
--- End of inner exception stack trace ---
at ArtOfTest.WebAii.BrowserSpecialized.InternetExplorer.InternetExplorerActions.LaunchNewBrowserInstance(Int32 timeout, ProcessWindowStyle windowStyle, String pipename)
at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser()
at WindowsFormsApplication3.Form1.btnLoginT_Click(Object sender, EventArgs e) in ...\WindowsFormsApplication3\WindowsFormsApplication3\Form1.cs:line 283
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.225 (RTMGDR.030319-2200)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
WindowsFormsApplication3
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/dudib/Desktop/Debug/WindowsFormsApplication3.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
imageClient
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/dudib/Desktop/Debug/imageClient.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ArtOfTest.WebAii
Assembly Version: 2011.1.712.0
Win32 Version: 2011.1.712.0
CodeBase: file:///C:/Users/dudib/Desktop/Debug/ArtOfTest.WebAii.DLL
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
UIAutomationClient
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationClient/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationClient.dll
----------------------------------------
UIAutomationTypes
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationTypes.dll
----------------------------------------
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
UIAutomationProvider
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationProvider/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationProvider.dll
----------------------------------------
UIAutomationClientsideProviders
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationClientsideProviders/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationClientsideProviders.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
ArtOfTest.InternetExplorer
Assembly Version: 2011.1.712.0
Win32 Version: 2011.1.712.0
CodeBase: file:///C:/Users/dudib/Desktop/Debug/ArtOfTest.InternetExplorer.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
5 Answers, 1 is accepted
Rank 1
After installing the test framework on the testing computer I get the following error
after IE is open but not navigating to the required URL.
Please advise.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.TimeoutException: Wait for condition has timed out
at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo)
at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)
at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser()
at WindowsFormsApplication3.Form1.btnLoginT_Click(Object sender, EventArgs e) in ....\WindowsFormsApplication3\WindowsFormsApplication3\Form1.cs:line 283
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.225 (RTMGDR.030319-2200)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
WindowsFormsApplication3
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/olegm/Desktop/Debug/WindowsFormsApplication3.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
imageClient
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/olegm/Desktop/Debug/imageClient.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
ArtOfTest.WebAii
Assembly Version: 2011.1.712.0
Win32 Version: 2011.1.712.0
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
UIAutomationClient
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
UIAutomationTypes
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
UIAutomationProvider
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
UIAutomationClientsideProviders
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
----------------------------------------
ArtOfTest.InternetExplorer
Assembly Version: 2011.1.712.0
Win32 Version: 2011.1.712.0
----------------------------------------
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version: 7.0.3300.0
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 6400 (20110822) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
I saw from your ticket #456467 that you are trying to execute our sample code given here . I've installed the same version of Testing Framework that you are currently using. I tested out the sample code again and it worked for me without the error you mentioned. Are you using a template when creating the test and which one? I would highly recommend you use the Web templates in a Visual Studio Test Project by:
Right clicking on your test project ->Add..-> New Item..->expand Test node->TelerikTestingFramework 2011.1 -> Web (see screenshot)
I'm attaching a project with the sample code in the VsUnit template. Please try to run it, and let me know if it works!
Greetings,
Plamen
the Telerik team
Rank 1
Hi,
I am getting the same issue in running my Test Studio tests with MbUnit. Tests works fine when executed from VS2010 but when executed thorough MBUnit, IE gets launched and then exception is generated. I have tried compiling the code in x86 and Any CPU settings and tried with both MBUnitx86 and x64 versions. Also, I have verified that IE 32 bit version is launched. Please let me know if I need to make any changes in my scripts so that they can get executed with MBunit.
Also, Gallio Icarus version 3.2 build 601 is giving exception on launch:
System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.BeginInvoke(Delegate method, Object[] args)
at System.ComponentModel.BindingList`1.ClearItems()
at Gallio.Icarus.Controllers.AnnotationsController.UpdateList()
at Gallio.UI.Events.EventAggregator.Send[T](T message)
at Gallio.Icarus.Controllers.TestController.Explore(IProgressMonitor progressMonitor, IEnumerable`1 testRunnerExtensions)
at Gallio.Icarus.Commands.LoadPackageCommand.Execute(IProgressMonitor progressMonitor)
at Gallio.Icarus.Commands.OpenProjectCommand.Execute(IProgressMonitor progressMonitor)
Reported by:
UnhandledExceptionPolicy
at Gallio.Common.Policies.EventHandlerPolicy.SafeInvoke[T](EventHandler`1 handlerChain, Object sender, T e) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Common\Policies\EventHandlerPolicy.cs:line 69
at Gallio.Common.Concurrency.Task.NotifyTerminated(TaskResult result) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Common\Concurrency\Task.cs:line 305
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
And if i try running Icarus from Gallio 3.3.1 zip, the tests are not displayed in UI on adding dll. I have even tried the MBunit sample provided but it also fails, IE gets launched and then exception is generated.
I'm sorry you are running into this problem.
I don't have much experience running MbUnit tests outside Visual Studio, but as far as I know if the code is compiled for x86 platform we should be able to run it. We are currently installing Gallio Icarus in our testing environment. We'll try to reproduce the issue locally and to find a solution. I'll let you know of the results tomorrow.
Thanks for your patience!
Regards,
Plamen
the Telerik team
Thank you for reporting the problem!
I have managed to reproduce this problem locally. I have filed a bug on this in our PITS system which you can track here: Public URL .
I have added Telerik Points to your account for discovering this bug for us.
It seams that we are not able to execute tests via Gallio Icarus using Internet Explorer and Firefox browsers, but the as seen in this video: http://screencast.com/t/d7Mp00aXB tests are running fine on Chrome.
As for the Gallio Icarus version 3.2. I'm getting the same error even If Gallio Text Explorer is empty, so I'm not sure that this a Test Studio problem, but we'll look into this further and if it is we'll fix that too.
Meanwhile, please use Visual Studio to execute your MbUnit tests.
Kind regards,
Plamen
the Telerik team