handanu
Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
TestComplete does not find an object in the requested time.
Hi, I use keyword testing for desktop application. I add a basic view of program and field that i have troubled with. In each test I use a checkpoint on an alert which stays on screen only 10 seconds. Normally testcomplete find this checkpointfield 3-4 seconds, but in some tests alert screen time becomes greater than 10 seconds, ~11-15 secs. So, when alert gone, my test fails. We use automation ids for checkpoint objects. Checkpointfield has an automation id but alert has not.(developers say they couldn't give the alert an automation id), Then I arranged the name mapping area from Sys Main Program Source_WindowHostWindow WindowHostWindow Alert Checkpointfield To Sys Main Program Checkpointfield (has automation id, extended find property is true) Source_WindowHostWindow (extended find property is false) WindowHostWindow (extended find property is false) Alert (extended find property is true) When Checkpointfield is under the Alert, testcomplete couldn't find the "WindowHostWindow". Or warns Source_WindowHostWindow's to change a property. I changed it but a few tests later it fails because testcomplete warns Source_WindowHostWindow's to replace with the previous one. That is why i drag and drop Checkpointfield under Main program. As I said above, this time testcomplete could take 10 seconds to find the Checkpointfield. If I move the mouse over alert, it will stay on the screen as long as the mouse is on it. But how could I do it in keyword test? Or any suggestions? I'm looking forward to your answers, Thank you very much. Testcomplete version:14.20 PS: Sorry if there is any grammer error.SolvedRe: Same object has different identities, so "the target object does not exist" error occurs.
There is operation field and contains find method. But I have to update like hundered steps. Because I use this alert as a checkpoint item and use it everywhere. But in name mapping I only drag and drop the alert from problematic parent to reliable parent. Just once. As if this were easier way.1.9KViews0likes1CommentRe: The window that needs to be closed first stays behind the other window.
I thought I wrote it clearly. Let me try more clearly. It is not about my program. It is about TestComplete itself. 1-)Firstly I open the Object Spy window. 2-)Then I click the test step for editing, it gives a warning (another window belonging test complete). 3-)I want to close the warning but I couldn't. Because it stays behind the Object Spy window. 4-)I couldn't close the object Spy window because of the warning ( TestComplete makes me close the warning first) 5-)I have to go to task manager and end the TestComplete. 6-)So I couldn't save my last works.1.4KViews0likes0CommentsRe: Same object has different identities, so "the target object does not exist" error occurs.
I guess I have found a way. I have changed the location of the object in name mapping and aliases section. I transport the object from problematic parent to reliable parent. When I run the test, it passes. But I still don't understand why alert window's identities changed project to project.2.1KViews2likes1CommentRe: Same object has different identities, so "the target object does not exist" error occurs.
Hi, Thank you or your reply. But this time I get "Ambigious recognition of the tested object" warning. It takes time to find the alert. I keep the alert window manually to see the warning.The alert window is invisible after a while (program's behaviour). So if I do not keep the alert manually, the alert will disappear and I will get an error again.2KViews0likes2CommentsSame object has different identities, so "the target object does not exist" error occurs.
Hi, I use property checkpoint on an alert. I get the target object does not exist error. Because the parent object was not found. When I check parent object's identities, with object Spy, I realize that some of the identities are different for example in name area old value was "WPFObject("xxxWindowxx","DesktopAlert")", new value is "WPFObject("xxxWindowxx","")". But when I create new project (with different namemaping) I see the alert window has the value WPFObject("xxxWindowxx","DesktopAlert")". And I turn my main project and check the window property it seems WPFObject("xxxWindowxx","DesktopAlert")". When I run the test it fails and I check property it is again "WPFObject("xxxWindowxx","")". I'm so confused. I have to fix it because I use this checkpoint in all tests. Thanks in advanceSolved2.1KViews0likes9Comments