Forum Discussion
tristaanogre
14 years agoEsteemed Contributor
Ivan,
Actually, I'm a little surprised you're not running into other problems. As you are creating tests on the one machine, you're updating things like the MDS file, the Script.tcScript file, and other such supporting structure files. When the scripts finishing running on the other machine, they will update those files as well if needed, potentially causing some corruption or other loss of settings.
In such a distributed environment, I would recommend using some sort of source control program like Mercurial/Hg or TFS or something. That way you can keep the actual code being worked on and code being executed local to the machine in question and you won't have any interference between the two. The check in/check out/get functions of your SC system would then allow you to make sure that your code is up to date on all machines in question regularly.
Actually, I'm a little surprised you're not running into other problems. As you are creating tests on the one machine, you're updating things like the MDS file, the Script.tcScript file, and other such supporting structure files. When the scripts finishing running on the other machine, they will update those files as well if needed, potentially causing some corruption or other loss of settings.
In such a distributed environment, I would recommend using some sort of source control program like Mercurial/Hg or TFS or something. That way you can keep the actual code being worked on and code being executed local to the machine in question and you won't have any interference between the two. The check in/check out/get functions of your SC system would then allow you to make sure that your code is up to date on all machines in question regularly.