Originally posted by cptusername on September 02, 2025
My project was executing tests just fine on Friday. This morning when I launched TestComplete, I was prompted to update, so I applied the update and am at version 15.77.6.7 afterward.
Now, when I attempt to run tests, a ‘Project not defined’ error is preventing any of my scripts from running. The errors seem to be occurring with my import statements for my custom python script files (i.e., import CashDrawerPage_Script).
The ONLY thing that changed since the last successful run is the TestComplete update. I had previously updated TestComplete a week or so ago when the last update was available.
How do I either resolve the error or else roll back to a prior version of TestComplete?
Latest Python Support. Support for Python version 3.13.3 has been added. This allows users to run and debug tests using the most recent Python runtime.
Originally posted by cptusername on September 02, 2025
Thank you, that is the likely culprit. We were running fine under TestComplete version 15.76, so have rolled back to that version for the time being while we figure out what we need to change to accommodate the Python runtime changes.
Again, nothing in our project changed between Friday and today, the sole change on any machine that had been running successfully on Friday was an update from 15.76 to this 15.77 version. A rollback has confirmed that is the cause of the change, as we are running fine again now under the prior version, so will now look into the Python support change(s).
Originally posted by mfoster711 on September 30, 2025
Did you find the root cause of this or is this just a break with TestComplete? I am now having this issue after updating one of our PCs to the latest version of TestComplete.
Originally posted by cptusername on September 30, 2025
The root cause involves how TestComplete manages the availability of its own objects across scripts. As a temporary measure, we’ve rolled back to version 15.76 pending the release of a fix, which support indicated earlier this month is a top priority.
Originally posted by mfoster711 on September 30, 2025
Thanks for the update! I am rolling back at to previous version. I just wanted to make sure this was not some Python change that I needed to update in my code.
Originally posted by cptusername on October 17, 2025
My team suspected that the issue persisted in this week’s 15.78 update, as it was not referenced in the release notes. As a result, we have remained on version 15.76. The most efficient workaround for us has been to revert to this earlier release. While it’s likely that re-architecting a significant portion of our project could eliminate the issue, the required effort is not feasible with our current timelines. Therefore, we continue to await an update that includes a permanent fix.
Originally posted by Michael_B on October 21, 2025
Fair enough. Thanks for the reply! We need the Chrome/Edge fixes in 15.77 to fix several projects, but the python bug broke others. Right now we are running mixed versions of TC as a workaround.
Be sure to mark or post the solution to help others out and/or to credit the one who helped you. 