Forum Discussion

wmtan01's avatar
wmtan01
Contributor
4 years ago

Iterative call to handler in TestComplete

Hi!   We use TestComplete to test multiple browsers all at the same time. RTC applications (which we have) require us to have 2 or more actors/users active during the test. This leads to us encount...
Scripting
AlexKaras's avatar
AlexKaras
Champion Level 3

Hi,

 

Personally I would try to eliminate the "Ambiguous Browser Recognition" warning. Can your testing be done using two different browsers, e.g. Chrome and Firefox?

To avoid iterative calls, you may consider use of public flag like in this pseudo-code:

 

Public bIsInHandler = False
...
Sub Warning_Suppress(Sender, LogParams)
  If (bIsInHandler) Then
    Exit Sub
  Else
    bIsInHandler = True
  End If

  if SuppressedWarnings.Contains(LogParams.MessageText) then
    LogParams.Locked = True
    Log.Message("Suppressed warning: " + LogParams.MessageText)
  end if

  bIsInHandler = False
End Sub

 

 

wmtan01's avatar
wmtan01
Contributor
4 years ago

Hi!

 

We are using two browsers but the namemapping is still under one browser. We do Aliases.browser where the identifier for browser is just the Object Type. It's not that great in terms of performance but it gets the job done for now. 

 

I'll try out this flag for in Handler and see if I still get the system pop up. Thanks!