After following the steps at https://docs.telerik.com/teststudio/advanced-topics/coded-samples/general/execution-extensions, I am having an issue with the name of the DLL placed in C:\Program Files (x86)\Progress\Test Studio\Bin\Plugins\.
This is a follow up to the issue mentioned at https://www.telerik.com/forums/writing-to-executioncontext-manager-log-in-oninitializedatasource#1581852. I'm starting a new thread as this is a different issue than the subject of the prior thread.
Visual Studio is creating TelerikExecutionExtension.dll. I copy this DLL to C:\Program Files (x86)\Progress\Test Studio\Bin\Plugins\ and when I run a test. The method OnInitializeDataSource fails to execute. If I copy TelerikExecutionExtension.dll to C:\Program Files (x86)\Progress\Test Studio\Bin\Plugins\ClassLibrary.dll (or simply rename the existing DLL) and rerun the test, the method OnInitializeDataSource is executed. The DLL name does not appear to impact the other methods within the IExecutionExtension implementation.
Telerik Test Studio Trace Log for both runs show the DLLs found and loaded, albeit in alphabetical order:
Only when named ClassLibrary.dll does the code in OnInitializeDataSource write to the log (red below). OnBeforeTestStarted and OnAfterTestCompleted write to the log regardless of DLL name (green below).
I can provide full logs from "C:\Program Files (x86)\Progress\Test Studio\Logs" and "C:\WebAiiLog", along with the test and test list files if a non-public drop location is available.
Thank you.
To close this thread out, it was determined that the extensions are loaded in alphabetical order and when method names collide, the 1st one loaded is used. The name of the DLL is only important in that it should be named anything alphabetically first when compared to the other DLLs in the plugin folders to ensure its methods take precedence.
Thanks to Elena for sorting this out for me.
Hi Todd,
Thanks for following up in the public thread as well. This is very kind of yours.