Hello,
I've been having an issue lately with running my tests. A simple link walkthrough (just testing all the main menu links) seems to fail once it starts clicking on links with this error:
ExecuteCommand failed!
BrowserCommand (Type:'Information',Info:'IsReady',Action:'NotSet',Target:'null',Data:'',ClientId:'Client_ec029db2-58f2-48d9-9472-75d877e9c0b3',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')
InnerException: System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.WaitForPipeDrain()
at ArtOfTest.WebAii.Messaging.Process.BrowserRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
Just wanting to know what's causing this. As recreating the step seems to work so its definitely finding the link.
I've been having an issue lately with running my tests. A simple link walkthrough (just testing all the main menu links) seems to fail once it starts clicking on links with this error:
ExecuteCommand failed!
BrowserCommand (Type:'Information',Info:'IsReady',Action:'NotSet',Target:'null',Data:'',ClientId:'Client_ec029db2-58f2-48d9-9472-75d877e9c0b3',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')
InnerException: System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.WaitForPipeDrain()
at ArtOfTest.WebAii.Messaging.Process.BrowserRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
Just wanting to know what's causing this. As recreating the step seems to work so its definitely finding the link.
14 Answers, 1 is accepted
0
Hello Andrew,
This error "System.IO.IOException: Pipe is broken." indicates that the communication link between Test Studio and the browser broke, for example the browser was closed in the middle of running tests, or a popup window was unexpectedly closed.
Does this problem always happen? If so can you recreate the problem, then go to Step Failure Details, find and click Export and send us the .zip file that generates? That will give us useful information to help diagnose what's causing this problem. A copy of the failing test, pointing out the failing test may help as well.
Regards,
Cody
Telerik
This error "System.IO.IOException: Pipe is broken." indicates that the communication link between Test Studio and the browser broke, for example the browser was closed in the middle of running tests, or a popup window was unexpectedly closed.
Does this problem always happen? If so can you recreate the problem, then go to Step Failure Details, find and click Export and send us the .zip file that generates? That will give us useful information to help diagnose what's causing this problem. A copy of the failing test, pointing out the failing test may help as well.
Regards,
Cody
Telerik
0
Andrew
Top achievements
Rank 1
Rank 1
answered on 18 Feb 2014, 01:52 PM
Here you go
0
Hi Andrew,
Thank you for the file. Please tell me what is happening in the browser when the step Click 'PublishCasesLink' executes. Is it possible that the browser is being closed by JavaScript and a new browser window is opening, sort of like a redirect to a new server is happening? If Yes, then this error is expected behavior. Test Studio is not expecting the browser to close, is actively trying to communicate with it as it is being closed and it results in this error. Is the next test step (step 6) a Connect to Popup step?
If Yes to both questions above, I'd like you to try turning on SimulateRealClick for step 5. Then Test Studio will move the mouse and click on the link, but won't try to communicate with the browser.
Regards,
Cody
Telerik
Thank you for the file. Please tell me what is happening in the browser when the step Click 'PublishCasesLink' executes. Is it possible that the browser is being closed by JavaScript and a new browser window is opening, sort of like a redirect to a new server is happening? If Yes, then this error is expected behavior. Test Studio is not expecting the browser to close, is actively trying to communicate with it as it is being closed and it results in this error. Is the next test step (step 6) a Connect to Popup step?
If Yes to both questions above, I'd like you to try turning on SimulateRealClick for step 5. Then Test Studio will move the mouse and click on the link, but won't try to communicate with the browser.
Regards,
Cody
Telerik
0
Nick
Top achievements
Rank 1
Rank 1
answered on 03 Mar 2014, 04:43 PM
hi im having the same problem. may i know if this was resolved? if so what was the solution. thanks.
0
Hi Niccolo,
We never heard back from Andrew, so we don't know what happened after my last response.
To assist you I need the same information (export of the Step Failure Details as I got from Andrew) and the same question to you: What is happening in the browser when the problem step fails?
Regards,
Cody
Telerik
We never heard back from Andrew, so we don't know what happened after my last response.
To assist you I need the same information (export of the Step Failure Details as I got from Andrew) and the same question to you: What is happening in the browser when the problem step fails?
Regards,
Cody
Telerik
0
Nick
Top achievements
Rank 1
Rank 1
answered on 07 Mar 2014, 10:26 AM
Hi Cody,
basically its a click step with a save button to submit a form. I've already ticked on the simulate real click but it still wouldn't push through.
basically its a click step with a save button to submit a form. I've already ticked on the simulate real click but it still wouldn't push through.
0
Nick
Top achievements
Rank 1
Rank 1
answered on 07 Mar 2014, 10:27 AM
sorry i forgot to attach the logfile.
0
Hello Niccolo,
We can tell from the stack trace it was trying to do a RefreshDomTree at the time it failed. Also we can see it was a timeout waiting for Test Studio IE plug-in to perform the command. Most likely the browser got stuck in some sort of busy state.
To overcome this I want you to try checking SimulateRealClick as shown in the attached screen shot. This stops the test step from trying to do a RefreshDomTree.
Regards,
Cody
Telerik
We can tell from the stack trace it was trying to do a RefreshDomTree at the time it failed. Also we can see it was a timeout waiting for Test Studio IE plug-in to perform the command. Most likely the browser got stuck in some sort of busy state.
To overcome this I want you to try checking SimulateRealClick as shown in the attached screen shot. This stops the test step from trying to do a RefreshDomTree.
Regards,
Cody
Telerik
0
Nick
Top achievements
Rank 1
Rank 1
answered on 09 Mar 2014, 11:31 PM
hi cody,
i have already checked on the simulate real click but unfortunately the step is still failing.
i have already checked on the simulate real click but unfortunately the step is still failing.
0
Hello Niccolo,
Since that did not work as expected, we need a way to repro the problem on our machines so that we can investigate and determine the root cause. Is there someway we can get direct access to the application? If this information is too sensitive to put into this public forum, you can open a private support ticket which only you and support can see.
Regards,
Cody
Telerik
Since that did not work as expected, we need a way to repro the problem on our machines so that we can investigate and determine the root cause. Is there someway we can get direct access to the application? If this information is too sensitive to put into this public forum, you can open a private support ticket which only you and support can see.
Regards,
Cody
Telerik
0
Nick
Top achievements
Rank 1
Rank 1
answered on 11 Mar 2014, 04:25 PM
Hi Cody,
I can send the video of the process in the private support ticket if that's ok.
Can you please provide the link to the private support?
I can send the video of the process in the private support ticket if that's ok.
Can you please provide the link to the private support?
0
Hello Niccolo,
1) Watching it happen in a video will not allow us to troubleshoot the problem and determine the root cause.
2) You create your own support tickets after logging in to your Telerik.com account - see attached screen shot.
Regards,
Cody
Telerik
1) Watching it happen in a video will not allow us to troubleshoot the problem and determine the root cause.
2) You create your own support tickets after logging in to your Telerik.com account - see attached screen shot.
Regards,
Cody
Telerik
0
Nick
Top achievements
Rank 1
Rank 1
answered on 11 Mar 2014, 06:41 PM
Hello Cody,
as much as i want to share to you the application, we are under legal agreement that no third party is allowed to access it, the least that i can provide is the video of where the error occurs. am not sure if that would solve anything but if there's another way to determine the error other than accessing the application please let me know and ill do what i can to provide you with all the necessary details.
as much as i want to share to you the application, we are under legal agreement that no third party is allowed to access it, the least that i can provide is the video of where the error occurs. am not sure if that would solve anything but if there's another way to determine the error other than accessing the application please let me know and ill do what i can to provide you with all the necessary details.
0
Hi Niccolo,
Our next best option is to capture a Fiddler trace of the application running normally in a browser. We can use that to simulate your web server and often we can reproduce problems enough that we can determine the root cause and the solution. Before starting the trace, please check both "Decrypt HTTPS" and "Store Binaries" so that the capture is complete. Also clear the browsers cache before starting as well so that the capture contains all web server traffic (it won't capture cached traffic).
Regards,
Cody
Telerik
Our next best option is to capture a Fiddler trace of the application running normally in a browser. We can use that to simulate your web server and often we can reproduce problems enough that we can determine the root cause and the solution. Before starting the trace, please check both "Decrypt HTTPS" and "Store Binaries" so that the capture is complete. Also clear the browsers cache before starting as well so that the capture contains all web server traffic (it won't capture cached traffic).
Regards,
Cody
Telerik