Framework tests throw ArgumentNullException under Firefox and Chrome with build 2014.2.618

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 22 Aug 2014 02:53 by Rosi Reddy

ADMIN

Konstantin Petkov

Created on: 23 Jun 2014 07:11

Type: Bug Report

Framework tests throw ArgumentNullException under Firefox and Chrome with build 2014.2.618

As a temporary work-around one can manually add the following registry key, see attached.

System.ArgumentNullException: Value cannot be null.
Parameter name: path1
Result StackTrace:
at System.IO.Path.Combine(String path1, String path2)
   at ArtOfTest.WebAii.Messaging.Process.HostsProxy.Start()
   at ArtOfTest.WebAii.Messaging.Process.HostsProxy.RegisterListener(MessageListener listener)
   at ArtOfTest.WebAii.Messaging.Process.ExecutionMediator.RegisterManager(Manager manager)
   at ArtOfTest.WebAii.BrowserSpecialized.Chrome.ChromeActions.LaunchNewBrowserInstance(Manager manager)
   at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
   at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser()

Attached Files:

FrameworkBinPath.png

3 comments

Rosi Reddy

Posted on: 22 Aug 2014 02:53

this path is not working and also latest build is still 2014.2.618. Appreciate if you provide any help on this.

https://www.dropbox.com/s/62d8m2ytaskzchu/Telerik.Testing.Framework.2014.2.630.msi

ADMIN

Daniel Djambov

Posted on: 02 Jul 2014 05:39

Telerik: issue is fixed and solution will be available in our next internal product release planned in the beginning of July 2014.

ADMIN

Konstantin Petkov

Posted on: 30 Jun 2014 13:51

Hello,

A custom build is created to address this problem on top of the 2014.2.618 build.
https://www.dropbox.com/s/62d8m2ytaskzchu/Telerik.Testing.Framework.2014.2.630.msi

Regards!