Hello,
We have been using the test framework in Chrome for a while now but when Chrome upgraded itself we needed the latest version of the extensions in order for our test suite to work. However, in that we lost something... Hard to say what...
what happens is when we do a find.byhtmlexpression then successive calls are not made and this exception is thrown:
if we switch browser type then the functions work, but we are required to test in chrome. Seems to be something with refresh dom tree
1. ExecuteCommand failed!, BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'be91a0a0-4a32-4290-981f-e3f553197f0e',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:''), InnerException: System.TimeoutException: Timed out waiting for command to be handled, at ArtOfTest.WebAii.Messaging.Process.BrowserHttpRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId, Int32 timeout), at ArtOfTest.WebAii.Messaging.Process.BrowserHttpRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId), at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
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.RefreshDomTree()
We have been using the test framework in Chrome for a while now but when Chrome upgraded itself we needed the latest version of the extensions in order for our test suite to work. However, in that we lost something... Hard to say what...
what happens is when we do a find.byhtmlexpression then successive calls are not made and this exception is thrown:
if we switch browser type then the functions work, but we are required to test in chrome. Seems to be something with refresh dom tree
1. ExecuteCommand failed!, BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'be91a0a0-4a32-4290-981f-e3f553197f0e',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:''), InnerException: System.TimeoutException: Timed out waiting for command to be handled, at ArtOfTest.WebAii.Messaging.Process.BrowserHttpRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId, Int32 timeout), at ArtOfTest.WebAii.Messaging.Process.BrowserHttpRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId), at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
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.RefreshDomTree()
1 Answer, 1 is accepted
0
Hello Taylor,
Anthony
the Telerik team
Can you share some code, preferably against a public site, that demonstrates this behavior?
I just ran a test in Chrome 17 with version 2011.2.1413 of Test Studio and had no issue using HTML Find Expressions. It also included lines to refresh the DOM tree.
Anthony
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
Test Studio Trainings