Logging issue on TC 15.80 (Python scripts)
Hello, After being stuck on version 15.67 for a long time (newer versions had the issue I described in this discussion: RuntimeErrors after upgrading to 15.68.8.7 | SmartBear Community (I also reported a ticket, but the issue was never fixed, and we didn’t try the workaround from that link because it was too risky for us), we finally decided to upgrade TestComplete to the newest version. This required some adjustments in our codebase, for example importing "the shim" as described in this article: https://support.smartbear.com/testcomplete/docs/scripting/specifics/python_tc_globalobjects.html e.g.: from tc import Log, Project, ... We no longer see any RuntimeErrors, so we were happy with this new version. However, we are now facing another issue: “disappearing” Log lines in TestLog during test execution. It looks like this: at the beginning of the test run all Log lines are present, but over time there are fewer and fewer of them, until TestComplete stops logging entirely. Scenario: If I run a group of two tests (let’s call them First and Second): First test contains most of the logs Second test has almost none But if I run Second and Third: Second test contains most of the logs Third test has almost none You can see the problem in the attached screenshot. In general, only the first few tests produce log entries. After that, Log entries are empty, which is a huge problem for us. Has anyone encountered this issue?
Work Arounds for "SystemError: intialization of md_mypyc did not return an extension module"
Hi, all. I'm having similar issues to this discussion post from a couple of years ago: importing of python module for simple-salesforce | SmartBear Community I know third-party libraries are a little iffy with TestComplete, but I was wanting to try to send out telemetry using Azure Application Insights, and I am able to successfully run my Test Script once before it throws the error from trying to import the module when I re-run the test just manually with TestComplete's Run Test Routine button. Was wondering if people have found any python script workaround if they've encountered similar errors. Thank you for your time and help!
TestComplete does not recognize my external libraries.
I have followed the documentation from following link: https://support.smartbear.com/testcomplete/docs/scripting/specifics/python.html I followed step by step; to install libraries to TestComplete python interpreter to the source folder: "...SmartBear\TestComplete 15\Bin\Extensions\Python\Python313\Lib". After closing TestComplete and opening it again, the interpreter is not being refreshed; not getting the newly added libraries I installed. It keeps throwing me an error as follows: ModuleNotFoundError: No module named 'imp'. The imported library I'm trying to use is a customized file with multiple classes. However, it does also happen for win23com.client and pillow libraries. import win32com.client from PIL import ImageGrab This seems to be an error with python 3.13, but I do not find a way to downgrade the python interpreter version from TestComplete. I do not find a way to fix this even after following documentation on how to install packages, either. Would appreciate your help on this, ThanksTestcomplete not executing interactive tests when triggered with TestComplete plugin .
Testcomplete is not executing interactive tests when triggered with TestComplete plugin . Testcomplete plugin version used in Jenkins job is 2.9.2 . The agent us connected to Jenkins master using JNLP for interactive execution . please help on this issue . The Testcomplete plugin invocation script is as given below: testcompletetest actionOnErrors: 'NONE', credentialsId: 'UTAAdmin_User_Pass', executorType: 'TE', executorVersion: '15.0', generateMHT: true, sessionScreenResolution: '1680x1050', suite: "${env.Pjs}", useTCService: true, timeout: '21600', useTimeout: true , useActiveSession: true Please find the log below 13:58:56 [TestComplete] The test execution started (TestAuto). 13:58:57 [TestComplete] Found TestComplete/TestExecute installations: 13:58:57 Type: TC, Version: 15.40.421.7, Path: "C:\Program Files (x86)\SmartBear\TestComplete 15\x64\bin\TestComplete.exe" 13:58:57 Type: TE, Version: 15.40.421.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 15\x64\bin\TestExecute.exe" 13:58:57 Type: TELite, Version: 15.40.421.50, Path: "C:\Program Files (x86)\SmartBear\TestExecuteLite 15\x64\bin\TestExecuteLite.exe" 13:58:57 [TestComplete] Selected TestComplete/TestExecute installation: 13:58:57 Type: TE, Version: 15.40.421.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 15\x64\bin\TestExecute.exe" 13:58:57 [TestComplete] [WARNING] The node is connected via Java Web Start (JNLP). In this mode, the "Run interactive user session" property of the TestComplete Test step is ignored. TestComplete (or TestExecute) will work in the current user session. 13:58:57 [TestComplete] Launching the test runner. 13:58:57 [TestComplete] [WARNING] Unable to publish test results (xml data is empty). [Pipeline] }
FindAll returns only one (first) element
Hi guys, I'm experiencing a weird problem. I have a mapped element, from which I need to get an array of elements. If tested in chrome/edge dev mode, the xpath of mapped element happily returns number of elements. But FindAll returns only one (first) element. Here is the code I'm using: function CompareElementsWithRefJSON(createNewRefFiles, setElementFlag, headerInputs, tabInputs, autocompleteMenu, selectPopUpMenu, tabsData, filePath) { let headerItems = headerInputs.FindAll('type','*',5000); headerItems = headerItems.toArray(); ... } I have a workaround, using FindElements, which works OK, but I don't like it, because it's unnecessary complicated: function CompareElementsWithRefJSON(createNewRefFiles, setElementFlag, headerInputs, tabInputs, autocompleteMenu, selectPopUpMenu, tabsData, filePath) { let formInputsXpath = GetXpathFromAlias(headerInputs); // This returns xpath of mapped alias object let headerParent = headerInputs.Parent; // Get parent element let headerItems = headerParent.FindElements(formInputsXpath); // Returns array of elements. Works OK. ... } So, any idea why FindAll returns just one element? BTW, it does not matter what PropName I use as the first parameter. The result is the same. Always just one element.
