We created a project and test on a local machine.
In that project we added in the settings menue/script options some references.
Then put it in a SVN Version Control.
We checked it out on another pc and opened in Telerik Test Studio.
What we get was that the project and test can be opened, but the references are not there.
We have to add it again to the project.
We want to work with more than one pc on that projects, so cannot add the reference each time, but all files are commited to the SVN.
I am wondering where the reference information are stored, so that we can share them, too.
Can you tell me, if there is a config file or how it is stored?
Thanks
Adriane
In that project we added in the settings menue/script options some references.
Then put it in a SVN Version Control.
We checked it out on another pc and opened in Telerik Test Studio.
What we get was that the project and test can be opened, but the references are not there.
We have to add it again to the project.
We want to work with more than one pc on that projects, so cannot add the reference each time, but all files are commited to the SVN.
I am wondering where the reference information are stored, so that we can share them, too.
Can you tell me, if there is a config file or how it is stored?
Thanks
Adriane
1 Answer, 1 is accepted
0
Hello Adriane,
Checking in your project in Test Studio Standalone will not check-in any files contained within the Project Folder. (or any files contained within Project Folder/Bin). So you can't attach the DLL to the project
Test Studio is using the DLLs from the folder they are contained in. For example, let's say your DLL was added from c:\myProjects\Project1\bin\MyDLL.dll
Test Studio will look for this DLL in the same location even if you check out the project on a remote machine. So the DLL will need to be in the same location on every machine.
Test Studio keeps the DLL paths in the <ProjectReferences> section of the Settings.aiis file. See the attached screenshot.
The best approach in your case might be(instead of changing the paths in the Settings file) to keep all your External DLLs in a shared location.
For instance let's say you have a machine with the hostname of MyMachine.
Now you can create a shared folder there called DllRepository. And you can access this folder from any machine in your network with the following expression:
Any projects you create - no matter on what machines - should reference all their assemblies from this location.
Now when you check in this project to source control and then check it out on a different machine - the only thing you'll need to do is to manually go to the shared location \\MyMachine\DllRepository. From there you'll need to manually add the required DLLs to the local GAC of the machine you're working on. This is not much work at all - you can just add all the assemblies in the folder to the local GAC - you don't need to know which ones the project actually uses.
Kind regards,
Plamen
the Telerik team
Checking in your project in Test Studio Standalone will not check-in any files contained within the Project Folder. (or any files contained within Project Folder/Bin). So you can't attach the DLL to the project
Test Studio is using the DLLs from the folder they are contained in. For example, let's say your DLL was added from c:\myProjects\Project1\bin\MyDLL.dll
Test Studio will look for this DLL in the same location even if you check out the project on a remote machine. So the DLL will need to be in the same location on every machine.
Test Studio keeps the DLL paths in the <ProjectReferences> section of the Settings.aiis file. See the attached screenshot.
The best approach in your case might be(instead of changing the paths in the Settings file) to keep all your External DLLs in a shared location.
For instance let's say you have a machine with the hostname of MyMachine.
Now you can create a shared folder there called DllRepository. And you can access this folder from any machine in your network with the following expression:
\\MyMachine\DllRepository
Any projects you create - no matter on what machines - should reference all their assemblies from this location.
Now when you check in this project to source control and then check it out on a different machine - the only thing you'll need to do is to manually go to the shared location \\MyMachine\DllRepository. From there you'll need to manually add the required DLLs to the local GAC of the machine you're working on. This is not much work at all - you can just add all the assemblies in the folder to the local GAC - you don't need to know which ones the project actually uses.
Kind regards,
Plamen
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
Test Studio Trainings