Posting the details of our usage of this separately.
Using Telerik Test Studio Stand Alone
Our project is checked into TFS with the following structure:
--TestFolders (Various other folders we organize our tests into)
--lib (library folder where we put our utility.dll)
We have created our utility.dll file and placed directly into the lib folder. Then in the Test Studio project setting we reference lib/utility.dll already within the project path, and in each coded test we add the reference to our namespace.
Please note, everything does work fine and properly. Tests run locally and remotely. Scheduled runs work fine and use the utility.dll. We are not having to manage the assembly as an installed dependency on the remote executors (which would be a deal breaker). Seems to work like we would expect and self deploys with the necessary libraries contained in the project like we would expect. But it seems the scheduled runs are not getting the latest version of this assembly from TFS when it runs.
We have noticed we need to manage the assembly directly in source control. Test Studio see's the lib folder we have checked into TFS, but it appears empty. We need to check out, update, and check in our library file manually.
Is it expected that the scheduled runs would get the latest version of the assemblies as well as the tests? Is there a best practice to this method which we are not following?