Auto Wait for CMD window can't be changed

Hi Ory,



I have discussed this situation with our development team and it seems that the CallObjectMethodAsynch was not designed to work in a script extension. However, since it works in other cases, we could try to make it work in your case as well. However, we need to reproduce this behavior locally in order to investigate it. Also, we could try to suggest something else if we had your application here. Is it possible for you to provide us with your application in any way (an installation package or a prepared virtual machine)? If this is possible, please contact us regarding this question using the Contact Support form.
 

Although in the video clicking the button took a long while (almost a minute), other tests (calling the method normally - not through script extensions) show that both the normal method and the ASync method take the same amount of time - about 13 sec (see below I re-recorded how a successful execution looks like). Therefore I'm unsure that we are even saving time using the ASync method...!

We have discussed this question before and have found that the time won by using an asynchronous call is significant:

According to the logs you posted, the asynchronous test works for 16 seconds while the usual test works for 35 seconds. In my opinion, this is a significant difference that shows that the asynchronous approach works in your case. The time spent while the asynchronous test is executed is needed for TestComplete to get the needed information on application objects and build the object tree. I think that there is no way to reduce this time.