Enter Case number reference for associated cases.

Case #

Status:

Type: APM as a Service

Old Article ID: 1845

Old Article Type: documentation

 

Information:

Detail the contextual information specific to the issue; i.e. Product, Version, Agent, System, etc.

  • Gomez Recorder
  • GPN
  • IE Agent
  • FF Agent

 

Describe the problem, from the user perspective

  1. How many types of wait actions in Gomez Recorder?
  2. What's the definition of them?

Clearly list the Steps to resolve the issue

  1. Wait For Page Complete
    • Wait until all objects in a web page are fully loaded. This wait will first wait for the "load" event of the browser. Then wait a "Page Complete Delay" time (default 250ms) to make sure everything is loaded. Then wait a "Pending Read Wait" time (default 3000ms) for any further asynchronous requests. Usually used to wait for page load.
  2. Wait For Network
    • Wait until no more network activity occurs. This wait event will be triggered by any network activity in 200ms after the previous action. It will wait until all network activities stop, then wait for another 200ms to verify there is no more network activity. Usually used to wait for AJAX and other asynchronous requests.
  3. Wait For Time
    • Wait for specific seconds. Usually used to wait for an event that only be available in a specific amount of time. Like a vote button available in 15 seconds later
  4. Wait For Validation
    • Wait until some element shows up in a page. Usually used to wait and verify some object.
  5. Wait For Event
    • Wait until certain event is triggered. Now, the Gomez Recorder only supports the following two events in this action: DOMReady & Load.
    1. DOMReady Event: DOMReady is a popular event in several JavaScript Frameworks. When a DOMReady event is trigered, web page elements may not be fully loaded but the DOM hierarchy has been fully constructed.
      • Implementation of this event varies in different browsers. For those browsers follow the W3C standards like IE 9+, Firefox 3+, Safari 5+, Opera 9+ and Chrome, it is implemented as the event “DOMContentLoadedâ€?.
      • So in the Firefox Agent, it will wait for the “DOMContentLoadedâ€? event (https://developer.mozilla.org/en/Gecko-Specific_DOM_Events).
      • In IE7 and IE8, it will wait for the "readystate"of DOM (http://www.w3schools.com/jsref/prop_doc_readystate.asp) being "complete".
    2. Load Event: A Load Event occurs when a web page is fully loaded. In the Firefox Agent it will wait for the "load" event (https://developer.mozilla.org/en/DOM/DOM_event_reference). In the IE Agent it will wait for the "DocumentComplete" event (http://msdn.microsoft.com/en-us/library/aa768329%28v=vs.85%29.aspx).

Note the underlying reason for the problem

  • Page not fully loaded on GPN
  • Page not fully loaded on local playback