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? ThanksSolved506Views0likes8CommentsTestExexute sometimes not recognizing object
When I execute my Desktop application using TestExecute, sometimes it would not recognize one of the objects. However, after rebooting the computer and restart the test again, the object could be recognized again. Test runs with TestComplete does not have this issue. How do I resolve this issue so that my tests can be reliably ran every time with TestExecute?59Views0likes2CommentsReset of the Test Execute enable extensions
Hello, We use Test Execute on our Azure Virtual Machines, and our test scripts rely on the legacy OCR module. Our team writes scripts using TestComplete version 15.54.x.x, with a similar version for TestExecute. Recently, we updated TestExecute to support testing web functionalities using the web module. We update to the version 15.71.4.11. However, after the update, we noticed that the legacy OCR module was disabled when running tests. We manually enabled the module in the extensions settings before running the tests: Unfortunately, the next day, some of our tests failed due to the OCR module being disabled again. It appears that the extension settings reverted to their default state, as if TestExecute had just been installed. We’re uncertain why this is happening, but we suspect it may be related to license availability. The TestExecute logs indicate that, at the time the OCR module failed, there was no available license for the machine: We believe the issue might occur when the machine attempts to execute tests while waiting for a license, and the connection is not successfully established. This could potentially cause the settings to reset to their default state. Our questions are: Why is this happening? What steps can we take to prevent this issue from occurring again? Thank you for your assistance. Best regards, Janusz49Views0likes5CommentsDoes TestComplete supports Avalonia UI framework?
Avalonia UI framework is supported by Testcomplete or not?Does it require to import any automation package to support the testing?It seems llike the native object recognition is not happening and the whole main window only treated as a single object here.Eventhough i have used the automation properties name,Id to the child objects.It is not getting identified.39Views0likes5CommentsWhat to do when UI element can't be selected by TC in a Keyword test?
I need to close a window of our Desktop Application, but the close box is inaccessible to TestComplete. Object Spy can't see it, it only sees the entire window. I found that I can directly call the CloseWindow method (or just Close) and that prompts the window to close, but our application always asks the user if they are sure they wish to close the window via a simple yes/no popup dialog. If I invoke closing via the method directly, then these yes/no buttons are not able to be interacted with at all by TC, despite TC being able to see them fine. If I manually click the close box, then let TC interact with the Yes/No buttons, they work fine. So it seems to me that something about invoking the method directly, is freezing TC out of being able to see that the Yes/No popup has appeared. I'd be happy to get either scenario working - getting TC to click the close button of the window, or invoking the method directly and getting TC to interact with the confirmation dialog. Any suggestions on how to deal with such a situation? I looked through the Freezing Diagnostics and tried to get it to tell me something, but it never produced any messages of any kind.39Views0likes4CommentsDoes Test Complete Support Syncfusion Grid Control with .NET Core
We are utilizing UFT automation Tool ( Previously QTP ) with Syncfusion QTP Add-in and planning to use different automation tool that will be able to identify Grids and control. The main idea is automation tool should able to identify our application objects(Object Identification) like we used from Syncfusion QTP Add-in. We are expecting some details or sample that can show us automation tool will support below Syncfusion products like below Essential Grid Essential Grid supports the following controls, SfDataGrid GridControl GridDataBoundGrid GridGroupingControl GridListControl SfListView Note - We are following below documentation as of now for QTP Add -in. https://help.syncfusion.com/windowsforms/testing/uft/supported-controls-and-methods71Views0likes6CommentsUnable to assert text in WPF ListView item
I am trying to assert the text of a specific cell in a WPF ListView item. but they are both identical except for the text. this is what I'm using to do the assertion but it's very flaky. It will always target "Asset 1" correctly when asked but will only sometimes target "Asset 2" when asked otherwise it targets the first in the list. Does anyone know how you can consistently target the cell you want when all attributes are identical?Solved48Views0likes8CommentsName Mapping not working on remote browser
The name mapping and test cases work fine on local browsers, but would complain about page or object not found when running headless remote browsers and in parallel testing. I have the following setup for browser name mapping: For headless setup I have: server = "localhost" capabilities = { "browserName": "chrome", "headless" : "true", "screenResolution": "1920x1080", "platform" : "Headless", "record_video": "true" } Browsers.RemoteItem[server, capabilities].Run(url) Is this the correct way to work with name mapping on headless browser?1KViews0likes15CommentsProblems by validating a tooltip of a wpf application
Dear community, I've encountered the following issue with a keyword test, as shown in the attached picture: The keyword test consists of 6 steps: Lines 1 to 4 and Lines 6 to 7. Line 5 is a manual interruption by the tester. The script in Line 6 triggers the visibility of the tooltip (of Component1), while the script in Line 7 validates the tooltip. Everything works perfectly if: - The tester executes the keyword test and stops at Line 5 using a breakpoint. - Subsequently, the tester resumes execution from Line 6 using the context menu item "Run from Selected Operation". However, the keyword test fails to find the tooltip if: - The tester executes the keyword test without stopping, so Lines 1 to 5 and Lines 6 to 7 are executed consecutively. What is the difference between these two scenarios? What could be the root cause of this problem and how can it be resolved? Thank you for your responses in advance! - Currently we use the TestComplete version 15.62.2.7 x64 - The tooltip is visible in both cases41Views0likes4Commentsobject recognition issue with Spy
When i'm trying to capture elements with spy it is showing below error. most of the time I'm not able to capture elements with "Drag and capture" or "Point and fix" features as it select whole window instead of the particular element. anyone facing this kind of issue?117Views0likes8Comments