locked
Questions about setting WebWaitForReadyLevel RRS feed

  • Question

  • Hi,

    We were having a problem with Jquery 2.x and coded ui test.  See this post for a synopsis of the issue:

    http://stackoverflow.com/questions/17849074/jquery-ajax-success-not-getting-triggered-with-coded-ui-test-project/21381319

    In the same post they recommend making this settings update to fix the problem:

    <add key="WebWaitForReadyLevel" value="3"/>

    We are in the process of testing this out but wanted to try and find more information about the WebWaitForReadyLevel and its possible impact on other tests.  We are having a hard time finding definitive sources of information about it.  Will this chnage have any negative consequences.  Can anyone point me to some MS documentation about this setting and all the possible options for values and what they mean.

    Thanks

    Jeff

    Tuesday, January 28, 2014 9:32 PM

Answers

  • Hi Jeff,

    WebWaitForReadyLevel :

    The default WebWaitForReadyLevel is 0 which is the most robust setting as timer and AJAX behavior is tracked. The tracking is accomplished by injecting script into the page. Setting the WebWaitForReadyLevel to 1 omits the injection of the timer script tracker. Setting the WebWaitForReadyLevel to 2 omits the injection of the AJAX script tracker. These values may be OR’d together so setting WebWaitForReadyLevel to 1, 2, or 3 will improve performance but the test will be less robust. If the addition of these injected scripts causes any behavior changes to the application try setting WebWaitForReadyLevel to 4 for timer problems or 8 for ajax problems or 12 for both. This won’t have much of an impact on performance.

    Modify the QtAgent32.exe.config file to change this behavior:

    <appSettings>

    <add key="EnableHtmlLogger" value="true"/>

    <add key="EnableSnapshotInfo" value="true"/>

    <add key="WebWaitForReadyLevel" value="3" />

    <add key="StopTestRunCallTimeoutInSeconds" value="5"/>

    <add key="LogSizeLimitInMegs" value="20"/>

    <add key="CreateTraceListener" value="no"/>

    <add key="GetCollectorDataTimeout" value="300"/>

    </appSettings>

    Best Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, January 30, 2014 3:50 PM

All replies

  • Hi Jeff,

    WebWaitForReadyLevel :

    The default WebWaitForReadyLevel is 0 which is the most robust setting as timer and AJAX behavior is tracked. The tracking is accomplished by injecting script into the page. Setting the WebWaitForReadyLevel to 1 omits the injection of the timer script tracker. Setting the WebWaitForReadyLevel to 2 omits the injection of the AJAX script tracker. These values may be OR’d together so setting WebWaitForReadyLevel to 1, 2, or 3 will improve performance but the test will be less robust. If the addition of these injected scripts causes any behavior changes to the application try setting WebWaitForReadyLevel to 4 for timer problems or 8 for ajax problems or 12 for both. This won’t have much of an impact on performance.

    Modify the QtAgent32.exe.config file to change this behavior:

    <appSettings>

    <add key="EnableHtmlLogger" value="true"/>

    <add key="EnableSnapshotInfo" value="true"/>

    <add key="WebWaitForReadyLevel" value="3" />

    <add key="StopTestRunCallTimeoutInSeconds" value="5"/>

    <add key="LogSizeLimitInMegs" value="20"/>

    <add key="CreateTraceListener" value="no"/>

    <add key="GetCollectorDataTimeout" value="300"/>

    </appSettings>

    Best Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, January 30, 2014 3:50 PM
  • Jack,

    Thanks for the reply.  When you said this - WebWaitForReadyLevel to 1, 2, or 3 will improve performance but the test will be less robust - what exactly does "less robust" mean?  What kind of problems might we see in our tests - missing clicks? element search problems? etc.

    Jeff

    Thursday, January 30, 2014 7:57 PM
  • Hi Jeff,

    Setting the WebWaitForReadyLevel to 1 omits the injection of the timer script tracker. Setting the WebWaitForReadyLevel to 2 omits the injection of the AJAX script tracker.

    Actually no official information about real problems it would impact, maybe it would impact the real test results since it omits something when the test is related to them.

    Have a nice day,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, January 31, 2014 2:10 AM