Contributions
WPF application not recognized as open
I've been testing a WPF application using TestComplete for a while now, with everything working well. I've recently installed TestComplete and that application on a new system, and I'd like to continue testing it there. However, on the new computer, TestComplete seems incapable of recognizing that my appliction is open. It reads the entire screen as a single object. I've checked the settings under UI automation, and they're all in order, but the probjem persists. How can I make TestComplete realize that the application is open?Solved1.7KViews0likes5CommentsRe: Convert FindChild object to NameMapping object
I see. Many thanks for the clarification; I hadn't realized that was how FindChild worked! Unfortunately, it doesn't look like WaitChild or WaitAlias will work for me. The object I need to reference may be one of several pre-mapped objects based on other factors in the test; that's why I was using FindChild, the results of which can change based on its parameter inputs. WaitChild and WaitAlias only have a depth of 1, and must search for specific object names, when I don't actually know in advance which object I'll need to reference.1.7KViews0likes1CommentRe: Convert FindChild object to NameMapping object
Thanks for the response! I'll admit I'm still a bit confused, though. As far as I know, switching to a NameMapping reference for an object that's already been mapped should only require reading the NameMapping repository, not writing to it. Is this not the case? Also, when you say "destroyed in memory", does that refer to TestComplete's memory, or the tested application's? The problem I'm currently trying to solve is that TestComplete loses track of the object when it is recreated within the tested application, so if you are referring to the tested application's memory, I'm not sure global variables would solve my problem.1.7KViews0likes3CommentsId property clarification
Hi all, Just looking for a quick clarification regarding the common-for-all property "Id". I understand that Id is a dynamic property. My question is, does Id ever change while a test is running, or is it static for the duration of each test? Thanks!Solved967Views0likes2CommentsConvert FindChild object to NameMapping object
Hi all, I've been running into a problem in my code in which I need to find any object that fits certain properties- not a specific object, but just the first one that matches the criteria- and then continue to reference the object initially found even if it's recreated by the system or its original identifying properties change. I can do the first part quite easily with Find and FindChild, but the second is giving me trouble. My current idea is to map all the objects that might fit the initial criteria with NameMapping. Then I can have my test initially locate an object with FindChild, but later reference it using NameMapping. However, it seems as though there is some invisible difference between the object variables produced by FindChild and those produced by NameMapping. Furthermore, I can't find any way to take an object variable produced by FindChild, and either convert it to rely on NameMapping instead, or create a new variable referencing the same object using NameMapping. Does anyone have any idea how to convert from a FindChild-located variable to a NameMapping one? Thanks in advance for any help you can offer.Solved1.7KViews0likes5CommentsRe: Adding method to "testobj"
Ouch, that's unfortunate. Locate performs some of the same functions as Find, so I was hoping to have a nice readable "Parent.Find(ChildProps).Find(ChildProps)" structure to my code rather than the current confusing "Locate(Locate(Parent, ChildProps), ChildProps)" format. Still, if that's what it takes, that's what I'll do. Thank you very much for your help!1.4KViews0likes0CommentsAdding method to "testobj"
I'm looking to create a method in javascript which can be called from an object variable in the same manner as common-to-all method- for example, "testobj.Find()". The method would be called Locate, and would perform operations upon the object. I've already written a working function which accomplishes the same thing by taking the object being manipulated as a parameter in the form of "Locate(Object ancestor, Variant propNames, Variant propValues, Integer depth)". However, I'd much rather be able to call the method in the form of "ancestor.Locate (propNames, propValues, depth)". From what I've been able to find so far, it seems like accomplishing this would take a script extension. Is this correct, or is there some way to do this in an ordinary script unit? If a script extension is necessary, would anyone be willing to give me a few pointers on how to get started on it? I currently have no experience with that particular functionality. I can post the code I currently have for the Locate function if necessary; I don't think it should be though. Thanks in advance for any help you can offer!Solved1.4KViews0likes2Comments