Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 19 May 2016 14:59 by ADMIN
ADMIN
Cody
Created on: 12 Sep 2014 15:00
Type: Bug Report
1
Test will not start if DownloadPath of data driven handle download is left blank
From ticket 858998

1) Configure a Handle Download Dialog to data drive the DownloadPath property
2) Leave blank the test steps DownloadPath property, expecting the test to still work because it is now data driven
3) Try running the test

Expected: The test to work
Actual: The test fails during initialization with:
'9/11/2014 4:26:07 PM' - System.ArgumentException: The path is not of a legal form.
   at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
   at System.IO.Path.GetFullPathInternal(String path)
   at System.IO.DirectoryInfo.Init(String path, Boolean checkHost)
   at System.IO.DirectoryInfo..ctor(String path)
   at ArtOfTest.WebAii.Win32.Dialogs.DownloadCompleteDialogCorrector..ctor(BaseDialog startDialog, BaseDialog completeDialog, String fileName)
   at ArtOfTest.WebAii.Design.IntrinsicTranslators.Descriptors.DownloadDialogHandlerDescriptor.CreateIE9Dialogs(Browser browser, List`1 dialogs)
   at ArtOfTest.WebAii.Design.IntrinsicTranslators.Descriptors.DownloadDialogHandlerDescriptor.CreateIEDialogs(Browser browser, List`1 dialogs)
   at ArtOfTest.WebAii.Design.IntrinsicTranslators.Descriptors.DownloadDialogHandlerDescriptor.InitializeDialogs(Browser browser)
   at ArtOfTest.WebAii.Design.Execution.ExecutionContext.SetDialogMonitoring(AutomationStepList steps, TestType testType)
   at ArtOfTest.WebAii.Design.Execution.ExecutionContext.SetDialogMonitoring(Test test)
   at ArtOfTest.WebAii.Design.Execution.ExecutionContext.SetDialogMonitoring()
   at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InternalExecuteTestIteration(Object codeBehindInstance, Boolean isDataDriven)
   at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.ExecuteDataDrivenTest(Test test, BaseWebAiiTest codeInstance)
   at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InternalExecuteTest(Test test, TestResult initializationResult)
   at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)
6 comments
ADMIN
Daniel Djambov
Posted on: 19 May 2016 14:58 
Telerik: after further investigation it seems the feedback scenario works fine, when DataEnabled property for Test is set to True, which is the normal case. Closing this feedback again. About the Autofac missing assembly, as Autofac is located in Test Studio bin folder, so it can be used by our runner, external runners like mstest cannot find it. To solve the problem, please put Autofac into GAC and tests will run.
ADMIN
Daniel Djambov
Posted on: 19 May 2016 06:56 
Telerik: Thank you for the feedback. It seems this is not working properly again in our latest product version - reopening this issue. However what you say about problems with mstest is a different problem, so if exists, please contact support to investigate and process the problem if any.
Mark
Posted on: 18 May 2016 20:52 
I still see this in 2016.1.330.0; the test runs fine from the Visual Studio test.run.all or selected, but when I run from mstest I see the symptoms described above; another symptom I saw while running mstest in the debugger is that Autofac
"Could not load file or assembly 'Autofac, Version=2.6.3.862, Culture=neutral, PublicKeyToken=17863af14b0044da' or one of its dependencies. The system cannot find the file specified."

the missing dependancies are
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
DCOMP.DLL
IESHIMS.DLL
ADMIN
Daniel Djambov
Posted on: 21 Jan 2015 13:44 
Telerik: the issue is fixed again and solution will be available in our next internal product release for planned for the end of Jan 2015.
ADMIN
Konstantin Petkov
Posted on: 15 Jan 2015 12:07 
Hello,

To our regret we have to revert the change as it caused more harm then good. This will be temporary until we implement a real fix of this scenario. The problem will be active with the internal build we are about to publish in the next days, however we will do our best to address the problem for the next official release.

Please excuse us for the temporary inconvenience!

Regards!
ADMIN
Daniel Djambov
Posted on: 03 Oct 2014 11:03 
Telerik: The issue is fixed and solution will be available in our next product release, planned in October 2014.
Create an account Log In
View
Type
Status