Document Complete - Indicates that the browser has finished rendering the page, including loading the entire DOM as well as all styles, images, and other resources. Document Complete is based on Chrome's onload event, with the exception of the Playwright test, which uses the Dom Complete event. The timing of these two events will usually be equivalent, as onload immediately follows Dom Complete. The only cases where they could differ would be due to any treatments handled by onReadyStateChange.
Webpage Response - There is no concept of this on the browser or in DevTools etc. This is defined by the Catchpoint agent, and we give you some means of controlling it. Essentially, the time it took from the request being issued to receiving the last byte of the final element on the page.
Non-Transaction Tests
- The agent waits up to 2000ms max to keep downloading data after Document Complete. The webpage response would be the end time of the last request to load or the max time of 2000ms. If there are asynchronous requests occurring after Document Complete then we will wait up to 5000ms post Document Complete for no network activity prior to ending the test.
- You have the option to tell the agent to end on Document Complete at the test level, in which case Webpage Response = Document Complete, using the option under advanced settings labeled Stop test post Document Complete after no network activity for X ms.
Transaction Tests
- The agent waits 500ms after Document Complete (onload) before performing any in-page action, like typing on a field or clicking on a button. It does this to make sure it does not fail to find some element on the page.
- On AJAX pages, our Transaction tests wait up to 2000ms for Document Complete. If Document Complete has not occurred in that span, the test will continue to the next executable verb in the script. (example:waitForElementPresent).
- In the case of Ajax interaction within the step, if clicking on button or field triggers some request on the wire, Webpage Response will include these timings (actions with AndWait will create new steps).
- If the in step activity does not cause requests on the wire and/or during the interaction time there were no requests are on the wire, it will not be included.
- Certain verbs like pause, waitForElementPresent, waitForUrl, or waitForNoRequest can cause the agent to wait longer, and if any requests are loaded during this period - their end time will determine webpage response.