Challenges with TestComplete 15.74 and SAP GUI 8.00
Introduction With the recent update to TestComplete 15.74, our team was eager to leverage the new features and improvements. However, during our testing with SAP GUI 8.00, we encountered several significant issues that have impacted our workflow. We hope that by sharing our experiences, other users facing similar challenges can join the conversation and find solutions together. Known Issues with SAP GUI 8.00 TestComplete has documented several known issues when working with SAP GUI 8.00. These include performance slowdowns and compatibility problems that can affect test execution. Despite these known issues, we proceeded with our testing, hoping the latest updates would mitigate some of these challenges. Problems Encountered During Testing: Playback Performance Issues with MS Teams Active When MS Teams was active during test playback, we noticed a significant slowdown. This issue persisted regardless of the version of MS Teams used. The playback speed was drastically reduced, making it difficult to complete tests in a reasonable timeframe. Password Containing an Exclamation Mark Another performance problem occurred when the password used in our tests contained an exclamation mark. However, the exclamation mark was not recognized as a character, so it was omitted during input. This led to a slowdown in playback and incorrect password entries, which prevented our test procedure from running. SAP Logon Crash During the execution of the transaction PA40, the saplogon.exe process crashed with the following details: Exception code: 0xC0000409 Process identifier (PID): 17472 Dump file: saplogon_ue_1527ac38.dmp The crash occurred while performing “OCR Checkpoint” and “OCR Action” operations. The system detected a stack-based buffer overflow, which could potentially allow a malicious user to take control of the application. Call to Action We are reaching out to the TestComplete and SAP GUI user communities to share their experiences and solutions regarding these issues. If you have encountered similar problems or have any insights, please join the discussion. Together, we can work towards finding effective solutions and improving our testing processes. Conclusion While the latest update to TestComplete brings many enhancements, it also presents new challenges, especially when used with SAP GUI 8.00. By collaborating and sharing our experiences, we can help each other navigate these issues and optimize our testing workflows. Feel free to share your thoughts and solutions in the comments below!
Qt6-Objects are not recognized
Hello, After Qt6.5-Upgrade of the software any Qt-Objects are not recognized by TestComplete (15.54, neuest at this moment) any more. The TestComplete Tests worked with the software with Qt6.2 or Qt5 without problem. Is there any way to make it work, other than waiting for TestComplete update? We are also wondering if we can find the Qt6.5(LTS)-Support plan somewhere. Thank you.please add Qt6.5 (LTS) Support
Qt6.5 (LTS) was released on April 3, 2023 and some bugs in Qt6.2 seem to be implemented only in Qt6.5. I believe Qt is widely used in desktop softwares and the demands of testings of softwares with newest Qt is large. However, TestComplete supports currently up to Qt6.2 and no update plan is published. We found that the newest TestComplete (15.54) cannot recognize any Qt-Objects in our software with Qt6.5. (Qt6-Objects are not recognized) Therefore, I would like to request Qt6.5 support urgently. Also, it would be helpful, if we could hear, when Qt6.5 is planned to be supported. Thank you.
How can we fetch ColumnIndex based on Column Name for Syncfusion Grid Control in Python
I was following below page for reference but didn't get also do we have more clear documentation for Syncfusion control ? https://support.smartbear.com/testcomplete/docs/app-objects/specific-tasks/grids/syncfusion-grid-control/index.html
objects previously recognized on desktop app
When beginning this project, I went through the exercise of getting objects to be recognized by test complete. I have a number of objects whose class is reported as WindowsForms10.Window.8.app.0.198698e_r8_ad1 or some variation. I was able to get recognitions with: adding appropriate the class names to Project/Properties/Open Applications/MSAA. I then began happily writing my test and enjoying every happy minute. What changed, you asked? I don't know. I make no changes to code or project properties. Immediately before observing this behavior, I had accepted the TestComplete dialog to update to the new version. Of course that is it, thought I. So I downgraded to TC 15.54.3.7 (which is the only version I have around. Waiting on SmartBear to tell me why my TC licenses are not showing up in the license manager.) I am experiencing the same problem in this previous version of TC. The only other thing I can think of that changed is that the AUT's database was restored. But the behavior that I am seeing in TC began before this. And in no way did this change the user interface. I looked at installed extensions, they are all installed except HP something something which I don't have. Any ideas from anyone on what might be going on? Thanks
Keys method sometimes adds period(.) in the middle of text
When using keys method to set the text in a field, sometimes Test complete adds unwanted period(.) in the middle of the required text (see screenshot). I have some test machines situated in Munich, I see this is predominantly on these machines. Any idea how to handle it?
TestComplete: Desktop app in Cobol and TC crash when I try to ObjectSpy it
I am looking into if I can automate an older company app written in COBOL, 32-bit. I am using TC 15.73 Pro. x86 I am running the app 'As an Admin' alone with TC 'As an Admin' After opening the desktop app, and trying to look at it in the Object Browser tree or ObjectSpy it, I get an app crash along with a TC crash. Any suggestions from folks here on options to try to get this to work? NetCOBOL COBOL ERROR REPORT <<Summary>> The application error occurred: Application : C:\ATOOL\haw$strt.exe(PID=00002138) Exception Number : UNDEFINED_EXCEPTION(C000041D) Generation Time : 03/17/2025(17:37:02) Generation Module : UNKNOWN Time Stamp : UNKNOWN File Size : UNKNOWN <<Detail>> Thread ID : 00001BA8 Register : EAX=000C05F2 EBX=03A68C20 ECX=03A68C20 EDX=00000000 ESI=000C05F2 : EDI=00000360 EIP=00000000 ESP=010FF2F8 EBP=010FF32C EFL=00010246 : CS=0023 SS=002B DS=002B ES=002B FS=0053 GS=002B Stack Commit : 00012000 (Top:01100000, Base:010EE000) [Could not output the machine language code.] Module File : UNKNOWN Address : 6343B530 etc. .....
