Forum Discussion
ray_mosley
14 years agoFrequent Contributor
Thanks for the responses. I will submit this to Support as an Enhancement Request.
I have other forum & support questions ongoing, especially dealing with using TestComplete with a source control system. 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. Yes, you can reduce the number of log files kept, but you are still creating your log file in the project tree by default.
Similarly, using the Log.SaveResults method simply saves a copy of the existing log file somewhere. The exising log file will still be put inot source control unless the script developer remembers to delete the log files.
Yes, you can set the location of the log files to be outside the tree, and that is better than nothing. 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).
Doing this provides several advantage:
1) I can blow away the C:\temp directory at will without affecting my script or the source control system.
2) using a permanent archive location also does not affect the contents of the source control system.
3) If continued modifications of the script are needed, I can still toggle the "run for the record" permanent archive location and the C:\temp location as needed, and do it in a single place using a boolean variable or even external sentinal file.
I have other forum & support questions ongoing, especially dealing with using TestComplete with a source control system. 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. Yes, you can reduce the number of log files kept, but you are still creating your log file in the project tree by default.
Similarly, using the Log.SaveResults method simply saves a copy of the existing log file somewhere. The exising log file will still be put inot source control unless the script developer remembers to delete the log files.
Yes, you can set the location of the log files to be outside the tree, and that is better than nothing. 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).
Doing this provides several advantage:
1) I can blow away the C:\temp directory at will without affecting my script or the source control system.
2) using a permanent archive location also does not affect the contents of the source control system.
3) If continued modifications of the script are needed, I can still toggle the "run for the record" permanent archive location and the C:\temp location as needed, and do it in a single place using a boolean variable or even external sentinal file.