ContributionsMost RecentMost LikesSolutionsRe: RuntimeErrors after upgrading to 15.68.8.7 Hello, 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... Re: RuntimeErrors after upgrading to 15.68.8.7 Unfortunately, no - we're still stuck with version 15.67. Re: RuntimeErrors after upgrading to 15.68.8.7 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. Re: RuntimeErrors after upgrading to 15.68.8.7 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. Re: RuntimeErrors after upgrading to 15.68.8.7 Yes, I am. We've been doing this for a long time, nothing has changed in this regard (same libraries as always). Is that any problem? Re: RuntimeErrors after upgrading to 15.68.8.7 Yes, that’s probably how it ends, but before that, I just wanted to know if anyone else has seen this as well. RuntimeErrors after upgrading to 15.68.8.7 Hello, 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? SolvedTest reruns issue with TC and TE 15.55 Hello, after installing TC 15.55, the test reruns behavior has changed. Before, when we had Rerun failed test items, times: (Current Project Properties->Playback) set to 1, it meant: max 2 times of test execution will be performed if test fails. Since 15.55 the same setting means 0 rerurns. For the same effect now it's necessary to set parameter Rerun failed test items, times to 2. In my opinion the previous behavior was more logical. Question is: is this a bug or functionality? I've seen nothing about that in release notes. Thanks Pawel Re: Python workflow and imports Re: Python workflow and imports Hi, one thing - are you aware that folders in Test Complete are sort of "virtuals", only for presentation purposes? I mean, despite you create and see folders in TestComplete (under script group) files are stored in flat stucture in hard disk (in Script folder). So in your case solution would be like that I guess: from a import ClassA class ClassB(ClassA): pass