Hi Harlan,
| Thanks for the responses. I will submit this to Support as an Enhancement Request. |
I've found your request in our DB. Thanks for your feedback.
| We have noticed that as we debug scripts, the number of log files grows and causes issues with merging essentially unwritten log (created while debugging scripts) to the source control system. |
Actually, we don't recommend that you keep log files in a source control system. By default, TestComplete doesn't add these files to the source control system as the test results node may contain a large number of log files (as in your situation). For more information on the files that are added by TestComplete, see the
List of Files Added to Source Code Control help topic. So, if you add the project files to the source control system manually, we recommend that you add only those files that are listed in the topic mentioned above.
| What I would prefer is to have my script default to a temprary location (for example, C:\temp\projectName\date\script_time) while I am debugging. WHen the script is completely developed and ready to be part of my regression suite, I can change the path to a permanent archive location (for example, \\Server\projectName\date\script_time). |
As Jared has said, the requested functionality is registered in our DB as a suggestion. As for now, I have only one workaround: you can try opening your project in a shared mode when you debug your tests. To learn how to do this, see the
Sharing Projects and Project Suites Among Several Testers help topic. When you open your project in shared mode for the first time, change the log location to the needed path, for instance
C:\temp\, and save the changes. TestComplete will save the specified setting only for the project opened in shared mode. So, when you open the same project in normal mode, the log location setting will contain the default value. That's how you can make TestComplete store several values of the mentioned setting.
I hope this information helps :)
