Forum Discussion
tristaanogre
13 years agoEsteemed Contributor
There's no particular option that will move things around like that.
However, if someone did a "save as" on the project files and saved them to a different folder, that will save the project file ONLY to the new folder and not any of the other files and linked files.
As for a best practice... don't use the "save as" to move projects from one folder to another... use the Windows file copying to copy folder to folder... That's KINDA a best practice...
A BETTER best practice is to utilize a source control system like TFS, VSS, Mercurial, or some such thing to create your repository of projects preserving all necessary file structures (which could include "non-standard" folder structures such as a "common" folder or something that is shared among multiple projects). Then, on your destination machine, do the necessary GET command to pull down the files in the same structure. While you're not doing development on your TestExecute box, you are operating against the source code of your tests and need to make sure that source code structure is preserved on all machines. Source control systems, in my experience, are the most reliable way of doing that.
However, if someone did a "save as" on the project files and saved them to a different folder, that will save the project file ONLY to the new folder and not any of the other files and linked files.
As for a best practice... don't use the "save as" to move projects from one folder to another... use the Windows file copying to copy folder to folder... That's KINDA a best practice...
A BETTER best practice is to utilize a source control system like TFS, VSS, Mercurial, or some such thing to create your repository of projects preserving all necessary file structures (which could include "non-standard" folder structures such as a "common" folder or something that is shared among multiple projects). Then, on your destination machine, do the necessary GET command to pull down the files in the same structure. While you're not doing development on your TestExecute box, you are operating against the source code of your tests and need to make sure that source code structure is preserved on all machines. Source control systems, in my experience, are the most reliable way of doing that.
Related Content
Recent Discussions
- 3 days agoMW_Didata