Fix for "Document is not ready to retrieve its markup" on firefox

2 posts, 0 answers
  1. Jan
    Jan avatar
    7 posts
    Member since:
    May 2016

    Posted 30 Jun Link to this post

    Hello! I have a test that uses both "Wait for exists" and "Wait for existsNot". This test work flawlessly for IE but when executed on firefox the "Wait for exists" actions fails 50% of the time and the "Wait for existsNot" fails 100% of the time. I have tried searching on the forums for a solution on the forums, but a delay execution action in this case simply will not do because the loading times are very variable and I want to emphasize efficiency on my test. If any solutions are available or more information on my problem is needed, please let me know, thanks!

    Unexpected error while waiting on condition. Error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
    BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'68776d95-33de-47f2-856c-028f02d34f3b',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')
    InnerException: ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
    InError set by the client. Client Error:
    mozCommandProcessor: ProcessInformationCommand(): Document is not ready to retrieve its markup.
    BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'68776d95-33de-47f2-856c-028f02d34f3b',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'mozCommandProcessor: ProcessInformationCommand(): Document is not ready to retrieve its markup.')
    InnerException: none.
     
       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()
     ---> ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
    InError set by the client. Client Error:
    mozCommandProcessor: ProcessInformationCommand(): Document is not ready to retrieve its markup.
    BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'68776d95-33de-47f2-856c-028f02d34f3b',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'mozCommandProcessor: ProcessInformationCommand(): Document is not ready to retrieve its markup.')
    InnerException: none.
     
       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()
       --- End of inner exception stack trace ---
       at ArtOfTest.WebAii.Core.Browser.RefreshDomTree()
       at ArtOfTest.WebAii.Core.Browser.ArtOfTest.Common.IAutomationHost.EnsureStateIsCurrent()
       at ArtOfTest.Common.Design.Extensibility.Descriptors.VerificationDescriptor.<PerformWait>b__f(IAutomationHost hst, DescriptorValueStore values)
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
       at System.Delegate.DynamicInvokeImpl(Object[] args)
       at ArtOfTest.Common.WaitAsync._worker_DoWork[T,V](Object waitParam)

  2. Elena Tsvetkova
    Admin
    Elena Tsvetkova avatar
    253 posts

    Posted 05 Jul Link to this post

    Hello Jan,

    Thank you for choosing Telerik Test Studio. 

    The detailed information you provide is quite helpful and I have few suggestions how your scenario could be handled.

    First would be to ask you if you have installed already the latest Test Studio R2 release. Please if you have not done so yet, use the 'Check for Updates' feature and upgrade to the recent R2 version.

    In case there is no change I would recommend to increase the ClientReady time for your test (please refer to the screenshot).

    If still facing the reported behavior please try to increase the time out time for the 'WaitForExist/Not' steps. Would there be any change in such case? 

    Please note that if the above suggestion do not affect the execution we will need to reproduce the issue on our side to be able to further investigate. So please consider the possibility to provide us your project and access to your application. 

    Thank you in advance for the cooperation! I hope to hear from you soon. 

    Regards,
    Elena Tsvetkova
    Telerik by Progress
     
    The New Release of Telerik Test Studio Is Here! Download, install,
    and send us your feedback!
Back to Top