Forum Discussion

marinb's avatar
marinb
Contributor
8 years ago

Logical paths in tcScript file

Currently we have various teams using the same TestComplete script unit collection. We would like to have all those projects point to the same script files, but the location a project can vary per te...
  • marinb's avatar
    marinb
    8 years ago

    I solved it by hacking editing the tcScript file and replacing all the relative folders with hardcoded versions.

     

    Using relative folders do not work if I want to move the project to another location. We develop on a pc where the project is located on the C-drive. Our build-environment drops the project on D:

     

    Our shared script units are on C: . Poof, can't find the script units anymore because the references are logical.

     

    Same with the log directory. If I check the log directory in current project properties, it literally reads 'C:\Temp\Log' , but in the test environment, it writes the log to D:\Temp\Log because in secret, in the .mds file the log dir is specified as '\Temp\Log'.

     

    I think that the log directory should read what's specified in the .mds file, not do a smart conversion because your project happens to be on the C-drive. This is just confusing.

     

    Some kind of option 'use logical paths' would be a nice to have.

AlexKaras's avatar
AlexKaras
Champion Level 3

Hi,

 

I would agree with Robert.

All paths in the project configuration files are relative the project file folder (the folder where the .mds file is).

And all paths in the project suite configuration files are relative the project suite file folder (the folder where the .pjs file is).

So everything should work as long as you preserve the folders structure.

marinb's avatar
marinb
Contributor
8 years ago

I solved it by hacking editing the tcScript file and replacing all the relative folders with hardcoded versions.

 

Using relative folders do not work if I want to move the project to another location. We develop on a pc where the project is located on the C-drive. Our build-environment drops the project on D:

 

Our shared script units are on C: . Poof, can't find the script units anymore because the references are logical.

 

Same with the log directory. If I check the log directory in current project properties, it literally reads 'C:\Temp\Log' , but in the test environment, it writes the log to D:\Temp\Log because in secret, in the .mds file the log dir is specified as '\Temp\Log'.

 

I think that the log directory should read what's specified in the .mds file, not do a smart conversion because your project happens to be on the C-drive. This is just confusing.

 

Some kind of option 'use logical paths' would be a nice to have.