Test Complete takes too long to find an object

Question

Hi,There's something it's bothering me and&nbsp;it's making my&nbsp;tests run slower than I'd like to.&nbsp;I'm having (performance)&nbsp;problems finding an object in the screen.&nbsp;The application under test (as&nbsp;any other) shows MessageBoxes to confirm/ask&nbsp;for user interaction. To find such view I use the following code:&nbsp;&nbsp;var base = Sys.Process("MyProcessName");
base.FindChild("ClrClassName", "MessageBoxView", 3);&nbsp;&nbsp;There's nothing wrong with it and it works just fine. There's only one quirk. It takes almost 2seconds to&nbsp;be able to find the view.BUT, during my investigation I found out that the second time Test Complete tries to find the view, it takes only about 50ms.That&nbsp;second-time behaviour doesn't benefit my tests at all, because that view is always destroyed (dismissed upon user interaction) and it's always "the first time" when Test Complete needs to find another MessageBox.&nbsp;Why is that happening? Why is it taking soooo long the first time?Is there a way to fix this behaviour? It doesn't take that long to find any other view within the&nbsp;main window of the application.

sergi · Answer

Marsha_R wrote:It's a good thing that I'm not testing TestComplete then! &nbsp;Two seconds out of my 70 minute test suite isn't worth pursuing.Sure 2 seconds out of 70&nbsp;minutes&nbsp;is nothing, but in my case, those 2 seconds (I have to interact about 45 times with a MessageBox) represent 90 seconds in a 15 minutes test, which is 10% of the time.&nbsp;That's why I need to know why this is happening and I was hoping for an answer from TestComplete but seems like I'll have to open a support ticket..

marsha_r · Answer

Could there be other calculations or objects loading in the background before that particular message box appears?

If you are using that same bit of code for all the message boxes, then I would suspect that there's something different about that particular box.

sergi · Answer

No, there's no background work ongoing.If I do&nbsp;the following, the second time I try to find that view&nbsp;it's immediate.No matter if the MessageBox is already being displayed when I execute my code or I do something to make the MessageBox be displayed, it takes almost 2 seconds to find it.&nbsp;var base = Sys.Process("MyProcessName");

// This takes ~1900ms
base.FindChild("ClrClassName", "MessageBoxView", 3);

// This takes ~50ms
base.FindChild("ClrClassName", "MessageBoxView", 3);&nbsp;&nbsp;&nbsp;

marsha_r · Answer

It makes sense that the second one would be faster because whatever is holding up the object isn't a problem any more by the time the first one executes.

Try putting a Delay=2000 right before the first one and see what happens.

sergi · Answer

I already tried putting a delay before and it made no difference at all.We could argue whether it makes sense that the second time is faster, but it doesn't make any sense that it takes so long to succesfully find a view that is already visible and in the&nbsp;first or second level of the root view.The same behaviour is observed when using the fullpath of the object.

Forum Discussion

Test Complete takes too long to find an object

Related Content

Endpoint takes reference expression literally

Test Complete 12 version takes long time to come out or struck when it doesn't find an object.

Script conversion takes several minutes.

[ReadyAPI-3.3.1] Taking very long to start

Launching TestComplete takes ages

Recent Discussions

Onscreen Object Selector Slowness

aqObject.CheckProperty() slowness

Problem with generated data table and keyword test

WebView2 support does not work

System checks for Object for every test