Current time: 04-05-2020, 01:34 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
measuring specific times via end-conditions
10-11-2011, 03:01 AM
Post: #2
RE: measuring specific times via end-conditions
(10-11-2011 02:47 AM)nilskuhn Wrote:  1)
The recorded time of tests scripted with the command setDOMElement is saved in file "1_report.txt": e.g. Time to DOM Element(id'myIdValue). Where is the time of tests scripted with the command setDOMRequest saved?
It overloads the DOM Element field and the time is recorded there (you can't have both).
Quote:2)
The "Time to DOM Element" seems to be integrated in WPT Monitor (DOM Time). The time measured via setDOMRequest can't be shown in monitor out of the box?
It should since it is written to the same field.
Quote:3)
Does the script-command "requiredRequests" records the time when the listed requests are fired (or their responses returned) like the commands setDOMElement and setDOMRequest do?
No, it does not record the times.
Quote:If not:
* Is it possible to measure the time when more than one specific DOM-Tree-Elements are loaded?
* Which time isn't recorded before the listed requests send their responses: Time to Document loaded, Time to fully loaded?
* If one of the required requests can't be loaded the test/measurement reaches timeout?
No, you can only record a single custom time in the current implementation. The test will report as a timeout error if the specified element isn't recorded (and I'm not sure but some of the times might be zero'd out, depending on the version of software).
Quote:4)
In my sripted tests using end-conditions often the time to start of rendering isn't taken correctly (0.000 seconds). Any ideas why that?
Render start is generally only measured for the first step of a navigation (when the screen is non-white). It can't (currently) measure the first visual change from a screen that has already been drawn.
Quote:In generally:
I want to measure specific times in the loading process of a site like the following example: images x, y and z are loaded, DOM-Tree-Element x is rendered and another element, e.g a select is usable.
Do you think adapting WPT for measuring souch specific times is a good idea? How would you assess the effort from 0 (nearly possible out-of-the box) to 10 (complete redesign of the browser-plugins for IE, Chrome and FF)?
You generally want to be REALLY careful over-instrumenting the DOM events because it generally has to poll the DOM looking for something so the granularity isn't great (100ms generally) and it can have a significant impact on the actual times (depending on how complex the DOM is). It's not hard to extend the current code (maybe a 3-4 effort just to cascade multiple times through the system) but other solutions might be better. If you control the page being measured then you might be better off instrumenting the page itself (onload handlers on the items you care about).
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: measuring specific times via end-conditions - pmeenan - 10-11-2011 03:01 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)