I recently upgraded to the latest version of TestComplete, and unfortunately, I’m experiencing issues. I’m still facing a RuntimeError originating from TestComplete’s native functions (I’m using it with Python scripts). The errors occur with functions like Log.Message, Log.AppendFolder, and others. However, the problem is quite random, as it’s not always the same line of code that fails. As a result, I’m unable to execute any tests at the moment and will need to downgrade to the previous version.
Is anyone facing this problem as well?
Yes, I know this article. If I added a new library now and it didn’t work, I would understand. The problem is that something that has worked for years has stopped working after this upgrade. Additionally, so far there is no evidence that it’s related to these 3rd party libraries; the error is not coming from them.
Anyway, I reported a ticket.
Unfortunately, I did not. I’m still in contact with tech support, but things are not going very well. We are still forced to use version 15.67, the last version without these problems. However, this is valuable input for me (sorry ) because it shows once again that this is not just our problem.
Originally posted by moonlight on September 24, 2025
I found a simple workaround.
Just create an OnStartTestEvent function, hook it up to TestComplete’s OnStartTestEvent, and add this line inside:
gc.collect()
Don’t forget to put import gc at the top of your module.
What this does: OnStartTestEvent is triggered right at the start of the test run, so calling gc.collect() there forces Python’s garbage collector to clean up memory before your tests begin.
What are your experiences with this workaround so far?
To be honest, I’m a bit hesitant to add this line to our codebase — our project is quite large.
On the other hand, staying stuck on the old version isn’t ideal either, and it seems unlikely that a fix from the development team will arrive anytime soon…
) because it shows once again that this is not just our problem.