Forum Discussion

david_vickers's avatar
david_vickers
Occasional Contributor
5 years ago

Waiting for OCR checkpoint to appear as screen loads

I'm using a OCR checkpoint to wait for a Citrix application and display a login prompt.  When the window appears there's a brief loading screen that displays before the login prompt that I'm using th...
Checkpoints
Keyword Tests
  • david_vickers's avatar
    david_vickers
    5 years ago

    AlexKaras  Discovered the reason for the "Invalid Text" error.  When selecting the parameters in the Keyword test area, for setting the parameter I was using a String type instead of Object type.  The solution from the support site actually works really well for me. The only issue with it is that it's a infinite loop, so I modified the sample code and used a for loop instead to emulate a 10 second timeout (I could also pass another parameter for the seconds) 

     

    function CheckTextContents(textToSearch)
{
  // Recognize the text contents of the specified onscreen object (Citrix window)
  var text = OCR.Recognize(Aliases.wfica32.wndTransparentWindowsClient).FullText;
  // Search for the occurrence of the specified substring in the recognized text
  return (aqString.Find(text, textToSearch, 0, false) > -1)
}
function WaitForText(textToWait)
{
  for (x = 0; x < 10; x++) { 
    if (! CheckTextContents(textToWait))
      Delay(1000);
    else
      break;
  }
}

     

     

     

BenoitB's avatar
BenoitB
Community Hero
5 years ago

KWT ou script ?

 

4 choices:

- add a delay of the maximum time needed to have this loading screen (aqUtils.Delay(delay in ms).

- add an ocr checkpoint to detect the loading screen prior the login ocr checkpoint

- changes the ocr value checked to take in account the text behind the loading screen

- change nothing but add error management on your login prompt and if failed make a retry

  • david_vickers's avatar
    david_vickers
    Occasional Contributor
    5 years ago

    Thanks BenoitB for the suggestions.  Here's my thoughts on them and correct me if I'm understanding this wrong:

     

    - I rather not relay of wait/sleep commands since it would slow down the script.  Plus they're not dependable since the loading screen duration could vary based on load/stress

    - I could add a checkpoint for the loading screen, but the risk is that after I check and then proceed, the loading screen may still be present.

    - There's no text behind the loading screen.  It displays on the screen and will disappear once the login completes and the application dashboard appears.

    - Error management/trapping may be the best approach. Is there a way to do this with a keyword test, or would it be best to do this via script?

     

    I'll also add the same behavior is happening when using an OCR Action.  Since my Citrix window is always displayed, switching between screens in the application is going to be a challenge because I run into the risk of grabbing text from the current screen with an OCR Action when I need the script to wait until the new screen appears.