Forum Discussion
Stopping time has more to do with the size of your logs than it does the idle time. For instance, if you are saving Visualizer images then the log can be pretty large.
There are ways to adjust that mentioned in here:
https://support.smartbear.com/testcomplete/docs/testing-with/visualizer/about.html
Hi Marsha,
I didn't see how that link was relevant.
I had to kill TestComplete in the Task manager after it hadn't stopped after 45 minutes.
I have my "Save log every" set to 2 minutes. So there should only ever be 2 minutes worth of log to process before stopping.
The script crashed at 1:02:23 a.m. because the sys.Desktop.activeWindow was not identified.
I stopped the code at 7:34:25 a.m.
At 8:15 a.m. TestComplete was still "Stopping..." with no way to force it to stop other than kill TestComplete
- Marsha_R6 years agoChampion Level 3
It was relevant if you have Visualizer turned on and are saving all those screenshots. Since I have no idea what your TestComplete settings are, I mentioned the biggest offender first.
When you run the test at night, does the machine go to sleep or is it still active when you come in?