Hi,
I'm using Test Studio 2013_2_1327 and when I try to add a COM reference (ieframe.dll) through Test Studio settings (Script Options\Add Reference) and save the project, the reference is not save in the Settings.aiis.
As a workaround I try to edit the Settings.aiis and add the reference manually (Interop.SHDocVw) inside the section "ProjectReferences":[..."Interop.SHDocVw"], and when I open Test Studio I can see that the reference is there.
Is not possible to add COM references? Is this a know issue?
Is my workaround safe or is there a safer way?
BR,
Luis
I'm using Test Studio 2013_2_1327 and when I try to add a COM reference (ieframe.dll) through Test Studio settings (Script Options\Add Reference) and save the project, the reference is not save in the Settings.aiis.
As a workaround I try to edit the Settings.aiis and add the reference manually (Interop.SHDocVw) inside the section "ProjectReferences":[..."Interop.SHDocVw"], and when I open Test Studio I can see that the reference is there.
Is not possible to add COM references? Is this a know issue?
Is my workaround safe or is there a safer way?
BR,
Luis
5 Answers, 1 is accepted
0
Luis
Top achievements
Rank 1
Rank 1
answered on 18 Feb 2014, 10:49 AM
Another thing...should I put "ProjectReferences":[..."Interop.SHDocVw"] or "ProjectReferences":[..."C:\Windows\SysWOW64\ieframe.dll"]
0
Luis
Top achievements
Rank 1
Rank 1
answered on 18 Feb 2014, 11:36 AM
Ok, forget the workaround.
I try both and despite thy show up on Test Studio settings\references, I keep getting "are you missing an assembly reference....".
I just noticed that the popup to add a new reference in Test Studio as the value ".NET assemblies" in the combo and that I don't have any more types. Is the problem due to the fact that this is a COM reference?
Can you give me a solution?
BR,
Luis
I try both and despite thy show up on Test Studio settings\references, I keep getting "are you missing an assembly reference....".
I just noticed that the popup to add a new reference in Test Studio as the value ".NET assemblies" in the combo and that I don't have any more types. Is the problem due to the fact that this is a COM reference?
Can you give me a solution?
BR,
Luis
0
Hello Luis,
In short you can only reference and use .NET type assemblies in Test Studio. A COM assembly and a .NET assembly have different entry points. As such a COM assembly cannot be directly used by a Test Studio project.
However if you create something called an Interop wrapper (a .NET DLL wrapper for your COM dll) for your COM assembly, that DLL should be usable by a Test Studio project. Disclaimer: We do not officially support this. If you can get it to work, all the more power to you. Pointing you in the right direction is the most we can assist in this effort.
I would be interested to hear what your end goal is, what automation challenge are you trying to overcome using a low level COM dll.
Regards,
Cody
Telerik
In short you can only reference and use .NET type assemblies in Test Studio. A COM assembly and a .NET assembly have different entry points. As such a COM assembly cannot be directly used by a Test Studio project.
However if you create something called an Interop wrapper (a .NET DLL wrapper for your COM dll) for your COM assembly, that DLL should be usable by a Test Studio project. Disclaimer: We do not officially support this. If you can get it to work, all the more power to you. Pointing you in the right direction is the most we can assist in this effort.
I would be interested to hear what your end goal is, what automation challenge are you trying to overcome using a low level COM dll.
Regards,
Cody
Telerik
0
Luis
Top achievements
Rank 1
Rank 1
answered on 19 Feb 2014, 09:26 AM
Hi Cody,
Thank you for your reply. We will try your solution.
Our purpose is to validate that the application user guide (a PDF help document) when it opens is positioned in the correct section (depends on the application context). Because that PDF opens in another window and Test Studio can't recognize any PDF elements we had to come up with another way to validate this. The best approach we found was to validate the window URL (it as the section).
Again Test Studio is unable to retrieve any window properties, therefore, after some goggling, we came across this possibility.
Can you suggest any other way?
Thank you,
Luis.
Thank you for your reply. We will try your solution.
Our purpose is to validate that the application user guide (a PDF help document) when it opens is positioned in the correct section (depends on the application context). Because that PDF opens in another window and Test Studio can't recognize any PDF elements we had to come up with another way to validate this. The best approach we found was to validate the window URL (it as the section).
Again Test Studio is unable to retrieve any window properties, therefore, after some goggling, we came across this possibility.
Can you suggest any other way?
Thank you,
Luis.
0
Hi Luis,
Ah I understand now the challenge you face. Yes validating a PDF that is loaded in a browser window is a difficult automation challenge. We have not come up with any recommended solutions to this problem.
Regards,
Cody
Telerik
Ah I understand now the challenge you face. Yes validating a PDF that is loaded in a browser window is a difficult automation challenge. We have not come up with any recommended solutions to this problem.
Regards,
Cody
Telerik