Hi,
After creating a couple of scripts with coded steps, which use a custom library file and testing them individually, we get an error for one of the scripts when putting it in a TestList.
The library is also used in a different script, which does succeed in the same TestList.
I already tried to remove the .cs file and create the coded steps once again, but this wasn't a solution.
Hopefully someone can point us in the right direction!
Thanks in advance
After creating a couple of scripts with coded steps, which use a custom library file and testing them individually, we get an error for one of the scripts when putting it in a TestList.
'1/8/2014 11:31:32 AM' - 'Fail' : 10. [Toelichting_CodedStep] : Rename PDF------------------------------------------------------------Failure Information: ~~~~~~~~~~~~~~~Exception thrown executing coded step: '[Toelichting_CodedStep] : Rename PDF'.InnerException:System.IO.FileNotFoundException: Could not load file or assembly 'TestLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.File name: 'TestLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' at ABN_AMRO_Internet.Toelichting.Toelichting_CodedStep()WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].The library is also used in a different script, which does succeed in the same TestList.
I already tried to remove the .cs file and create the coded steps once again, but this wasn't a solution.
Hopefully someone can point us in the right direction!
Thanks in advance
1 Answer, 1 is accepted
0
Hi Reinout,
Regards,
Boyan Boev
Telerik
To make this work you have to copy your dll to the ROOT directory of project, then just refer it from that location.
Note this will work only if you put the dll in the root directory as it is described at the bottom of this article. Test Studio will not find references to a DLL in the subfolders of the project folder. These include: bin, Properties, obj, Data, Backup, TestResults, Results, TestLists, and Profiler Configurations.
Hope this helps.
Regards,
Boyan Boev
Telerik