Hi Allen and Martin, Thank you both for your feedback.
I have written heaps of code to validate every field of a large windows app and have just started test execution. Sorry to gripe but I am finding the log file management very labour intensive. I am running TestComplete on my XP machine and TestExecute on a Win7 PC which I have to connect to using Remote Desktop (as it is not on our domain).
1) Creating the log file only at the completion of testing has caused me issues. Hours into test execution the script crashed the PC. As there was no log file created it was not clear which part of the code caused the crash.
2) As the log file is created at the end of testing, I don't see Martin's point of writing a script to auto archive the log at the end of testing.
3) My logging is verbose so that the log files are so large that they cannot be opened in IE.
4) Due to (1) & (3) I have broken my test down to test one form at a time. Ther are over 120 forms so I manually have to edit my DDT to select just one form then execute the test. Some runs are performed multiple times, so that I end up will a collection of log files - some valid, some junk. The log files only have a date stamp for a name and I have no idea which is which. So I have to copy the files from the remote PC to my PC, import them into TestComplete. Sort the wheat from the chaff, delete the chaff and give the good logs a meaningful name within the TestComplete log. However, this does not rename the files which are still anonomous. The files cannot be renamed (now that we know which is which) because this breaks the log file displayed within Test Complete.
I am sure that there must be an easier way to do all this. I just thought that I would give you some feedback, in the hope that this can all be simplified.
