Auto Wait for CMD window can't be changed

Hi Ory,





You describe a known problem of TestComplete 7.20 and older. If you have this version of the tool, please install the latest one (7.52 or 8.10) and let me know if it works as expected.

Hi David,



Thanks for the reply. I am using TC 8.10 (thats the only version I have been using).



What does this mean?

Hi David,



Thanks for your suggestion. I have been playing with this and here are the (somewhat strange) results:

To see if executing the command asynchonously helps, I have added a break point in the next operation after the ClickButton. As you can see in the first 2 attached videos [CardSharl_click_ESL_button_-__normal.swf] and [CardSharl_click_ESL_button_-__asunchronous.swf] it seems that indeed the suggested method helps (in the asynchronous one it gets to the breakpoint straight after clicking the button, where in the "normal" one there is a delay before getting to the break point).



So, to make sure that this solves the issue I have timed the full operation (that sub I'm executing) both in "normal" and asynchronous mode ([CardSharl_click_ESL_button_-__asunchronous_Full.swf] and [CardSharl_click_ESL_button_-__normal_Full.swf]) and to my surprise I have found out there is no difference in the total time the sub executes - they both finished in around 28-30sec... Far more then what I'd expect that sub to execute in!



So back to the starting point I suppose. What do you think?



PS

I have also attached the script file Im executing in the videos (it's the last sub).

Hi Ory,





I think that the delay in your case is the time of access to the CMD window. Since the window is accessed in both cases, when you click the button synchronously and asynchronously, there is no difference in the execution time. The delay is just moved to another line of the code.





You can check this by logging messages to the test log after every test code line and then seeing in the test log which lines were executed for a long time.

Thanks for the answer.



I have done as you suggested and attached the results.



It seems that when I click the button normally there is a 10s delay before the next line (which finds and accesses the window). In the other case (performing the click in an a synchornous manner) the delay shows when the CMD window is accessed.



Does this confirm what you were thinking was happening? Is there any way for me to minimize that time?



Thanks

Hi Ory,





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.

Hey David,



Thanks for the response. According to your suggestion, I have been using the Asynchronous call for the last 3-4 weeks, and it does seem to be improving the run time of my tests.



However, I've noticed that sometimes (without any pattern) the next line of code fails. I've tried to wrap this with all kinds of logic to handle it, but eventually it all comes back to the Async call.



I'll explain.

Here is the relevant piece of code:

---------------------------------------------------------------------------------------------------------------------------

    'The following line clicks the Run ESL script in an Asynchronous manner (which proved to be faster)    

    Call Runner.CallObjectMethodAsync(Aliases.CardSharkCryptoSW.dlgCardShark.RunESLScriptBtn, "ClickButton")

    Call aqUtils.Delay(10000, "Waiting for ESL script to run..")

    

    'Getting the ESL CMD Window

    'Turn vb error handling on

    On Error Resume Next

      Set ESLCMD = GetESLCMD

    'If vb script exception occured terminate and restart card shark

    If Err.Number <> 0 Then

         ....

---------------------------------------------------------------------------------------------------------------------------



So basically the delay after the call (3 seconds) is to ensure that the CMD window that the button invokes is displayed (when done manually the CMD window is displayed immediately). However the Function "GetESLCMD" (whose whole purpose is to find that CMD window) often returns with a vbScript error "Object not found" (or something similar, error code 424) and hence I've added the exception handling.

I've noticed that increasing the delay does not seem to help, in fact is looks like the delay after the Asynch call is causing issues. If you view the attached screen captures you will see then when a 3 seconds delay is used the button appears to be only clicked after the delay, when a 10 seconds delay is used the button does not seem to get clicked at all!

I've also shown in the video that adding an empty Log.Message call between the asynchronous call and the delay seems to solve the issue..? (I have not verified this, it's just an idea)



Note: I've even tried to move the delay to after the "On Error Resume Next" line with similar results.



What's going on? Should I maybe go back to calling the click button in a synchronous manner?

Hi Ory,





The Object not Found errors are test execution errors and they cannot be handled by the VBScript exception handling feature. I suggest you moving the timeout into the procedure that searches for the CMD window. Please let me know if this works for you.

...

    'The following line clicks the Run ESL script in an Asynchronous manner (which proved to be faster)    

    Call Runner.CallObjectMethodAsync(Aliases.CardSharkCryptoSW.dlgCardShark.RunESLScriptBtn, "ClickButton")

    

    'Getting the ESL CMD Window

    Set ESLCMD = GetESLCMD

    'If ESL CMD windows is not found...

    If ESLCMD is Nothing Then

...





Function GetESLCMD

  Dim CMDwText, CMDWindows

  Dim Timeout, EndTime

  

  Timeout = 10000





  EndTime = GetTickCount + Timeout

  Set GetESLCMD = Nothing





  ' Try to find the ESL CMD window within the timeout period

  Do

    'Finding all matching CMD Windows

    CMDWindows = GetCMDWindows

    'Checking that a CMD Window has been found

    If Not isNull(CMDWindows(0))  Then

        'Go through found windows and find the ESL Script one

        For i = 0 To UBound(CMDWindows)

          CMDwText = CMDWindows(i).wText

          If InStr(CMDwText, "C:\AFC\cardshark\CardShark 30.8.0004.sea>set ESLPATH=config\ESL\sea") <> 0 Then

            Log.Message("ESL CMD Window found")

            Set GetESLCMD = CMDWindows(i)         

          End If

        Next

    End If

    

    If EndTime < GetTickCount Then

      Exit Do

    End If

  Loop While GetESLCMD is Nothing

  

  ' Check whether the window was found

  If GetESLCMD is Nothing Then

    Log.Error "ESL CMD window is not found"

  End If

End Function

Hi David,



Thanks for your suggestion.



The Exception thrown was:

An exception occurred in the "ESLScripts" unit at line 45:
Microsoft VBScript runtime error
Object required: 'GetESLCMD'An exception occurred in the "ESLScripts" unit at line 45:

Microsoft VBScript
runtime error

Object required: 'GetESLCMD'



And was due to the following line (when GetESLCMD was not returning an object):

Set ESLCMD = GetESLCMD



So effectively I was capturing a VB Script error with my exception handling.



I now understand this was due to not setting GetESLCMD to Nothing when it can't find the correct window. I have updated my scripts according to your suggestion and will keep you updated about the results.



However, I still think there is a problem with the Async call followed by a Delay, obviously my updated scripts now do not have a delay, but none the less it might be a good idea for you to look into this.



Thanks for the help.