wmtan01
Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Iterative call to handler in TestComplete
Alright after trying out that fix which in theory should fix it up as it definitely would not allow recursive calls, the system popup still showed up. Something weird is definitely happening here. Here is the log when I'm not doing any handler on the event: Notice that there is only 1 instance of the warning. And no other warnings after it. But with the handler here is what's happening: It seems that the OnLogWarning event is being triggered repeatedly causing the handler to be repeatedly be called, though not by the handler itself.. since as the log shows bIsInHandler is False (that's what I'm logging)... And to make it even weirder, I modified the handler to just be this and it still triggered the system pop up. Based on the original log there should just be 1 warning, so only 1 trigger of the event, unless the event itself is causing another event which seems to be the case... bIsInHandler = False set SuppressedWarnings = CreateObject("System.Collections.ArrayList") SuppressedWarnings.Add "Ambiguous browser recognition." Sub Warning_Suppress(Sender, LogParams) Log.Message(bIsInHandler) 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) 'Log.Error("TEST") 'end if 'bIsInHandler = False End SubRe: Iterative call to handler in TestComplete
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!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 encountering "Ambiguous Browser Recognition" warnings during runtime. To make logs cleaner I attempted to make an OnLogWarning Event handler that checks if the message is "Ambiguous Browser Recognition" and if it is, don't log it. It seems to work fine but sometimes TestComplete throws a popup saying that iterative calls were being made to the handler. Which doesn't make sense since I'm not calling Log.Warning on my handler which was suggested in the info page for the OnLogWarning event. Here's my handler: set SuppressedWarnings = CreateObject("System.Collections.ArrayList") SuppressedWarnings.Add "Ambiguous browser recognition." Sub Warning_Suppress(Sender, LogParams) if SuppressedWarnings.Contains(LogParams.MessageText) then LogParams.Locked = True Log.Message("Suppressed warning: " + LogParams.MessageText) end if End Sub I really want to clean up the logs and remove these warnings, is there an easier way to do this? Or if someone can tell me why my handler would do an iterative call that would be great.Execution Plan causes freeze/not responding
Hi, Anyone else experiencing difficulty switching to the Execution Plan tab? We're triggering execution runs manually sometimes which means we have to work in the Execution Plan window. I noticed that after an execution, when I want to go back to the Execution Plan the system freezes but goes back after a few minutes. It's not happening when we're just scripting so it might be related to the fact that I just did an execution. What are the possible causes of the poor performance of the Execution Plan tab/window?Running in RDP - Chrome/Edge Chromium not performing actions
Hi, I've noticed that the UI does not update on some of our test cases even though the test script says that it should do something. For example the following KWT should type in a message and hit send: This KWT is called multiple times in testing of our chat application. When I was watching the execution I noticed that the Chrome/Edge window (in the video I will attach it is Edge) seem to be frozen, like the actions were not being done but for some weird reason the results of those actions are still being seen by the 2nd participant in the chat (opened in Firefox). See attached video for clarity. Notice that in the middle part of the video, the application actually updated I think it was when the click to the Vehicle Info tab was done. I've seen this happen multiple times in various machines and I let it be because it did not seem like it was breaking things. But then one of our machines started this behavior: So the test logs were saying that "Send" button was clicked but it was not as indicated by the compounded messages. Expected would be similar to what was in the video. And now this actually causes the test cases to fail because our application only enables certain controls once a message is sent. And in this case those messages that were supposed to get sent did not get in. I only see this happening on Chrome/Edge Chromium. I'm wondering if the Smartbear Extension could be broken for when executing test cases with multiple browsers open. It is working correctly on my local and on some of our other Run Agents as well. I've tried it both for the latest TestComplete version and the one before that 14.6X. I hope someone can shine a light on what's happening and how I can fix/do a workaround.
