Closing HTML pop up window says client is not connected to remote to be able to process command

Update: This test run threw a different exception in the same step for the same test.

 

Failure Information: 
~~~~~~~~~~~~~~~
ExecuteCommand failed!
BrowserCommand (Type:'Information',Info:'IsReady',Action:'NotSet',Target:'null',Data:'',ClientId:'Client_8bb993bb-fcdb-4a90-ab6b-621ad051c32d',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')
InnerException: System.Runtime.Serialization.SerializationException: End of Stream encountered before parsing was completed.
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at ArtOfTest.WebAii.Messaging.Process.PipeCommand.FromBinary[T](Byte[] bytes)
   at ArtOfTest.WebAii.Messaging.Process.PipeCommunication.ReadCommandFromPipe[T](PipeStream pipe)
   at ArtOfTest.WebAii.Messaging.Process.BrowserRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)

InnerException:
ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
BrowserCommand (Type:'Information',Info:'IsReady',Action:'NotSet',Target:'null',Data:'',ClientId:'Client_8bb993bb-fcdb-4a90-ab6b-621ad051c32d',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')
InnerException: System.Runtime.Serialization.SerializationException: End of Stream encountered before parsing was completed.
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at ArtOfTest.WebAii.Messaging.Process.PipeCommand.FromBinary[T](Byte[] bytes)
   at ArtOfTest.WebAii.Messaging.Process.PipeCommunication.ReadCommandFromPipe[T](PipeStream pipe)
   at ArtOfTest.WebAii.Messaging.Process.BrowserRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
 ---> System.Runtime.Serialization.SerializationException: End of Stream encountered before parsing was completed.
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at ArtOfTest.WebAii.Messaging.Process.PipeCommand.FromBinary[T](Byte[] bytes)
   at ArtOfTest.WebAii.Messaging.Process.PipeCommunication.ReadCommandFromPipe[T](PipeStream pipe)
   at ArtOfTest.WebAii.Messaging.Process.BrowserRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
   --- End of inner exception stack trace ---
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Core.Browser.IsReady()
   at ArtOfTest.WebAii.Core.Browser.WaitUntilReady()
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Actions.Click(Element targetElement)
   at ArtOfTest.WebAii.Controls.HtmlControls.HtmlControl.Click()
   at ArtOfTest.WebAii.Controls.HtmlControls.HtmlControl.Click(Boolean isClosing)
   at ArtOfTest.WebAii.Design.IntrinsicTranslators.Descriptors.ClickActionDescriptor.Execute(Browser browser)
   at ArtOfTest.WebAii.Design.Extensibility.HtmlActionDescriptor.Execute(IAutomationHost autoHost)
   at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.ExecuteStep(Int32 order)
------------------------------------------------------------
'8/21/2018 12:41:10 PM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.

Not sure if this is related, but changing the recorded step to click an element to a coded step leads to the step failing earlier. As a coded step, the element to be clicked is considered invalid and not even clicked. (Similar to https://www.telerik.com/forums/invalid-input-type-error )

 

Stacktrace as coded step:

Failure Information: 
~~~~~~~~~~~~~~~
Exception thrown executing coded step: 'Click 'FirstSelectProviderArrow''.
InnerException:
System.ArgumentException: Invalid tag name 'span' for this control. Control was expecting 'div'
   at ArtOfTest.WebAii.Controls.Control.CreateInstance[TControl](Element e, Boolean throwIfNull)
   at ArtOfTest.WebAii.ObjectModel.Element.As[TControl]()
   at ArtOfTest.WebAii.TestTemplates.HtmlElementContainer.Get[TControl](HtmlFindExpression expr)
   at ArtOfTest.WebAii.TestTemplates.HtmlElementContainer.Get[TControl](String[] clauses)
   at LT_Claims.Pages.InternalProviderSearchPage.get_FirstSelectProviderArrow() in c:\Users\matt.smith\Documents\Test Studio Projects\QH_QA_TEST\QA Test\Pages.g.cs:line 2165
   at LT_Claims.Pivit_MAT_IPAdmitIn.Pivit_MAT_IPAdmitIn_CodedStep() in c:\Users\matt.smith\Documents\Test Studio Projects\QH_QA_TEST\QA Test\Pivit incl. claims\MATTests\Pivit_MAT_IPAdmitIn.tstest.cs:line 77
------------------------------------------------------------
'8/21/2018 1:53:24 PM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------

What confuses me most about this exception is that the find settings for the element in question expects that the tagname is exactly span, but the stacktrace states that the control was expecting div.

Hello Matt,

Thank you for all details shared. 

As of the initial errors you have shared I suspect that the Internet Explorer might be running in compatible mode or the application has a meta tag to force the browser to act as a lower version of IE. That could be similar to the following: 


So please double check the compatibility view settings, try to turn that off and try to run the test - what the execution will be like? 

If this is not helpful you might need to verify the existence of the meta tag with the developers of the application. If it turns out this is the case I have to admit that Test Studio supports the latest browsers versions and we could not commit that any lower IE version will work as expected since there might be missing functions in the previous IE versions which are implemented in our execution process. 

The concern you have listed in regards the element from the failed step is probably related to the recorded element and the modified find expression. You might have modified that to locate span but it was initially recorded as a div element. You could double check the Control type of the element  in its properties - select the element in the Elements explorer and click on properties in right mouse button context menu. On the right of the Test Studio window the property should become active and the first field is the one which holds that information. Please refer to the screenshot. 

Probably this is related to the specific structure of the application under test and to be able to solve that you will need to add the element to the repository manually. To do so you could start a recording session using the 'Run To' options from the step context menu. Once the test is on the desired page enable the highlighting and using the Elements Menu locate the element in the DOM explorer. Then select it and add it to the Elements repository. You might need to modify the find expression of the newly added element as well. 

I hope the above notes will be useful for you. Though in case you have any other questions please let me know! 

Regards,
Elena Tsvetkova
Progress Telerik

Hi Elena,

Thank you for your quick and thorough reply!

Regarding compatibility mode, Internet Explorer is not running in compatibility mode. The test opens an initial window, which opens an html pop up window, which opens a second html pop up window where clicking a button there fails with the above exceptions. The initial window has 

 

The first html pop up window has

 

The second html pop up window, the one that fails when clicking a button that closes it, does not have any meta tags.

Does setting compatibility tags to use IE=edge interfere with Test Studio?

 

Regarding the element expecting div but finding span, you are absolutely correct. Recording the element initially selected a div, and I modified the find expression to look for span. Out of curiosity, why is adding a new element required instead of updating the existing element's ControlType to ArtOfTest.WebAii.Controls.HtmlControls.HtmlSpan not fix the issue?

 

I manually added the element being clicked as a span. Using a recorded click step continued to fail for the same exception. However, changing the click to a coded step and updating the click call to be foo.Click(true) instead of the default passing in false seems to have fixed the issue. I just ran the test about 5 times without seeing the exception, when previously the test failed >50% of the time.I don't see how updating that element and passing true would have fixed the issue, but I'm hoping that it actually did. Any insight would be greatly appreciated!

 

Thank you for all your help!

Hello Matt,

Thank you for the additional detailed information. 

I would like to test few things in regards the element adjustment on my end and will get back to you with further details as soon as possible. 

The other issue related to the compatibility settings how IE will be used is probably the root cause for the failures. Though I would need some time to further investigate that as well. 

Please excuse me for the delay and for any inconvenience caused with that but I would like to try few things on our side to provide you an accurate reply on both topics. Therefore I will appreciate if you allow me some time for that!

Thank you in advance for your understanding!

Regards,
Elena Tsvetkova
Progress Telerik

Hello Matt,

And thank you once again for your patience.

I managed to perform some testing on my end and here is what I can add in this discussion. 

The meta tag used in the application under test will not be a trouble as it forces IE to act as the latest available IE version. Since this is not supposed to be causing troubles I would like to ask for the following: You mentioned there is a click performed in the popup which actually closes the popup - please let me know if I have misunderstood that. 

Though if the above is correct I would like to ask you to try enabling a step property named 'ClosesBrowser' for that click step that closes the popup browser. Then try executing the test and verify the behavior. 

In regards the elements and if it is better to add the step in record mode again or modify the element's control type there shouldn't be quite a difference. If any issue, though, appear it might so that the element was somehow corrupted during the recording process. This is not expected but could happen. So if updating the element's find expression and control type doesn't work you could try to manually add the element and a step against it. 

What you have changed in the coded step is actually the step property I mentioned above and you have set that to true. So since this is the target element for the click action which closes the popup it seems this will be the solution. Please try to enable that in the UI and disable the coded step so that we could find out if that is improving the success rate of execution. 

Thank you very much! I look forward to hearing back from you! 

Regards,
Elena Tsvetkova
Progress Telerik

Hi Elena,

Thank you for taking the time to test these. Enabling the 'ClosesBrowser' step appears to have resolved the issue. 

Regarding the issue of modifying the element's control type not working, I recorded the element again and set the test to use the new element. I will let you know if I see the issue again. 

Thank you for all your help!

Hello Matt,

Thank you for the feedback! i am pleased to know we managed to find out the solution for that misbehavior! 

In case of any troubles please do not hesitate to contact me back! 

Regards,
Elena Tsvetkova
Progress Telerik

Hi Elena,

Unfortunately, today I saw the same error appear that the client is not connected to remote to be able to process command after closing an html pop up window through a step with the 'ClosesBrowser' step property enabled. 

I added logging after the step that closes the html pop up window and noticed that the Manager.ActiveBrowser.Url was still the Url for the html pop up window. Also, Manager.Browsers.Count listed 2 browsers, when I expected only one. 

So far I have tried adding a coded step of Manager.ActiveBrowser.WaitUntilReady() after closing the html pop up window, but this fails with the same error message. 

Thoughts on why this is happening and what I may be doing wrong?

Thanks,

Matt

Hello Matt,

Thanks for all details shared. 

is there any chance that the behavior of application got changed? 

As of now you shouldn't have a Close Popup step since the Click step uses the property 'ClosesBrowser'. Could you please execute the test to the step before that Click step using Run->To Here and once the recorder is attached to the popup click the button again to re-record the same action. This should record the Close Popup step as well. 

Once you have these new steps available disable the previous Click step and execute the test with the newly recorded click (which does not have enabled 'ClosesBrowser' property) and the Close Popup step. What the behavior of the so configured test will be? 

I am looking forward to hearing back from you! 

Regards,
Elena Tsvetkova
Progress Telerik

No, the behavior under test has not changed.

I did as you recommended and re-recorded the action to record a new Click step and a Close Popup step. Then I disabled the previous Click step that had the 'ClosesBrowser' property enabled, so I am left with a Click step that does NOT have the 'ClosesBrowser' property checked and a Close Popup step.

Unfortunately, this causes the test to fail every run. The test begins by navigating to a url, clicking a link to open a popup, connecting to that popup, clicking a link to open a second popup, filling out some info, clicking a link that closes the second popup, taking more actions, and clicking a link that closes the original popup. The second popup still closes despite the Click step not having the 'ClosesBrowser' property enabled. The new Close Popup step now closes the original popup, despite the partial PopupUrl not being found in the popup's url. This causes the next step to fail, because the step waits for an element on the original popup. The element is no longer being found, because the Close Popup step incorrectly closes the original popup.

Thank you for your assistance!

Hello Matt,

Thank you for your cooperation. 

As you have reopened a ticket from over a month ago I would like to cross check few details which might have changed for that time. Please let me know your output for the following: 
- Test Studio version
- which browser fails to connect to the popup and its version
- is there a browser which handles the scenario and its version? 
- is this a local quick execution or a test list execution? If it is test list, is it a remote or local execution? 

Then I will really appreciate if you could record a short video of the faulty execution and send it via this thread - will that be possible? 

Thanks in advance for your cooperation!

Regards,
Elena Tsvetkova
Progress Telerik

Test Studio version: 2018.2.606.0

Browser that fails: Internet Explorer 11

Browser(s) that handle the scenario: None. Currently only testing in IE, which fails.

Execution type: Local quick execution.

 

Unfortunately, due to the nature of the site under test and its sensitive data, I am not able to record a short video. Also, the failure only happens intermittently.

Having discussed a number of scenarios and attempted solutions, I'll describe the faulty execution again to avoid having to dig through old posts. A test navigates to a page, clicks on an element that opens an html popup window. Once connected to the html popup window, the test clicks another element that opens a second html popup window. This second html popup window is a search feature, so the test enters some data, clicks a button, waits for search results, and then clicks a search result. The act of clicking the search result closes the second html popup window (the window closes regardless of whether the click action has the 'ClosesBrowser' checked or unchecked, and regardless of whether there is a close popup step). The test then should be on the original html popup window and waits for an element's value to contain info from the selected search result. The test intermittently fails between clicking the search result on the second html popup window and waiting for the value of an element on the original html popup window to contain info from the selected search result. When the test fails, the logs show a stacktrace mentioning "System.InvalidOperationException: This client 'Client_e66ee583-28c5-4e43-918d-aa7f6a236a37' is not connected to remote to be able to process command" with a different client ID.

Hello Matt,

Thank you for time and continuous cooperation on this issue. 

The structure of the popups to automate is quite complex as you described it. The intermittent nature of the issue will complicate our investigation as well. Though, there is still something we could give a try to. Please generate the application log file during a failing test run - clear the log, then execute the test and once it fails collect the log file to send it zipped via this thread.

Very useful will be if you could record a video to share for reference. Though if there are any security concerns about sharing a video recording of the application under test we could conduct an online meeting to review the issue in details. 

I am looking forward to hearing back from you! Thanks once again! 

Regards,
Elena Tsvetkova
Progress Telerik

Thank you for your patience. Sorry for the delayed reply. Other matters arose that required my attention this week. 

Attached is the zip of the log. The test runs with two local data rows. Disregard the first failing run, as it fails for a known issue. The second run fails with the client not connected exception. 

I completely re-recorded the test following your previous recommendation to uncheck the "ClosesBrowser" step and add an explicit close pop-up step. The step that fails is a click action not marked as "ClosesBrowser". Following this click is a close pop-up window step, but the test failure stops the test from reaching the close pop-up step. 

Test Studio version: 2018.2.606.0

Browser: IE 11

Execution type: Local quick execution.

 

Thank you again for your help to track down this issue. 

I should also note that this time the test failed on a different step, but with the same logic. The test fails when closing a pop-up window.

I was recently notified that I should post issues like this in the support center instead of the forums, so closing this issue and moving it to https://www.telerik.com/account/support-tickets/view-ticket/1344787 

 

Thank you for all your help!

Hi Matt,

Thank you for the note and submitting a support thread on the topic. I will proceed closing this thread and continue our discussion in the mentioned ticket. 

Regards,
Elena Tsvetkova
Progress Telerik