Contributions
Re: WaitAliasChild taking minutes when Object does not exist
1. Would changing the name mapping have an effect if I am looking for a direct child though? While the mapping isn’t full on the parent object, it finds the parent object with no issue. However it is the direct child of the object I am calling WaitAliasChild on or even WaitNamedChild on. So wouldn't any extra name mapping only help if there was a deeper hierarchy between the object I am looking for and the object I am calling the wait on? Which is there is no deeper level in this case. For instance if I had object hierarchy of A B C D E F I am calling C.WaitAliasChild() to find D, but say I did not have B mapped it shouldn’t affect it in this case I would think since wouldn't it only check anything after C? Or in the case of non-existence does it ignore the hierarchy of C and check other parts of the document or the entire thing. 2. By that does that mean the name mapping properties? At the very least between the name mapping hierarchy and the selected properties it is definitely unique. I also tried adding some more properties but that doesn't seem to change anything. 3. Cant actually try this one since since I am using an older version of TestComplete so can’t speak for it. Also since In the name mapping I dont have extended find enabled isn't it effectively spending those more than 2 minutes just checking maybe 8 or so objects over and over? Or would it also ignore that and check all levels under the object.1.6KViews0likes0CommentsRe: WaitAliasChild taking minutes when Object does not exist
Even if I don't check for the exists property it doesn't seem to affect the time it takes so Im not sure if that would be the issue. Would you recommend using a different waitX method to check for an objects existence then though?1.6KViews0likes0CommentsRe: WaitAliasChild taking minutes when Object does not exist
Also after some more testing it seems to take around 45 seconds in Internet Explorer (while the 2ish minutes happens in Chrome). Also the wait time does seem to have an affect but only if you make it longer than those times and even then it seems to be a bit off.1.6KViews0likes0CommentsWaitAliasChild taking minutes when Object does not exist
I am trying to use WaitAliasChild to check whether an object exists or not. When it does exist it finds its normally and quickly. However when it does not exist it seems to take around 2 minutes to resolve saying it is waiting for the object regardless of what timeout time I put into it. I know the parent object that I'm calling it on does exist at the time of it running, and the child I'm looking for is also a direct child, but I'm not sure why it would take so long. Is there a reason for this that I might not be seeing?1.6KViews0likes8Comments- 2.1KViews0likes4Comments
Re: Object Browser wont expand
I test on both Chrome and IE and I am aware of Chrome updating and it needing patches, but it does not seem to recognize and processes running including any browser. Also, I think I've had that problem in some cases but TestComplete would still recognize Chrome as there just not recognize anything going on in it.2.1KViews0likes6CommentsRe: Object Browser wont expand
It probably would have been good to include that in my initial post but it can also be hard to figure out exactly what information would be relevant to a problem if you do not know what might be causing the problem. But the machine that it is being tested on and the TestComplete version are the same as when it was previously working. The Browser has most likely updated and the webpage being tested has been updated however I would not think those would be directly related to TestComplete not recognizing any other processes running. As for a change on the machine that is using TestComplete that might cause some kind of issue...that might be a possibility if applicable in this situation.2.1KViews0likes0Comments