W3C home > Mailing lists > Public > public-web-perf@w3.org > May 2013

[ResourceTiming] Test Cases Reviewed

From: Jatinder Mann <jmann@microsoft.com>
Date: Wed, 1 May 2013 16:01:59 +0000
To: "'public-web-perf@w3.org'" <public-web-perf@w3.org>
Message-ID: <0c43fed4393b4afc9062d017b2ec23de@BLUPR03MB065.namprd03.prod.outlook.com>
Microsoft has reviewed the Resource Timing test cases submitted by Intel and Google. Some these test cases should be approved, while others may have test bugs.

The following 14 test cases look correct and should be moved to the approved folder:
http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_connection_reuse.html
http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_dynamic_insertion.html
http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_frame_initiator_type.html
http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_ignore_data_url.html
http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_redirects.html
http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_reparenting.html
http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_script_types.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_clear_resource_timing_functionality.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_cross_origin_redirect.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_cross_origin_redirect_with_timing_allow_origin.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_cross_origin_resource_request.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_on_shrink_buffer_size.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_same_origin_redirect.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_timing_allow_cross_origin_resource_request.html

We believe the following test cases may have test bugs.

This test cases still uses the non-standard window.location.origin: http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_attribute_order.html.

This test case fetches 2 identical resources (with different query strings) to test if a 304 will create an entry. Looks like the test case expects a duplicate entry to be created, even though I would expect that we do not create a resource timing entry for the duplicate. Let's discuss in today's conference call: http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_cached.html.

This test fetches a resource that doesn't exist (returns 404) and is expecting 0 resource timing entries. Looks like the test expects that the entry shouldn't be created. I wanted clarification if step 3.7 (if fetching the resource is aborted for any reason, abort the remaining step) means that we should not add this entry. Let's discuss in today's conference call:
http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_ignore_failures.html

This test case doesn't seem to run in any browser; there are no passes or failures: http://w3c-test.org/webperf/tests/submission/Google/resource-timing/html/test_resource_initiator_types.html.

This test cases creates 3 resources before ResourceTimingBufferSize is set to 2. Per spec text, "if the maxSize parameter is less than the number of elements currently stored in the buffer, no elements in the buffer are to be removed. The maxSize parameter will apply only after the clearResourceTimings method is called." The number of entries won't be truncated if they exist before a lesser buffer size is set: http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_buffer_size_restriction.html.

Seeing that we just updated the onresourcebufferfull callback behavior in the spec, we should review to see if these test cases need to be updated:
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_buffer_full_when_populate_entries.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_buffer_full_when_shrink_buffer_size.html
http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/test_resource_timing_store_and_clear_during_callback.html

Thanks,
Jatinder
Received on Wednesday, 1 May 2013 16:05:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:35 UTC