- From: Nic Jansma <njansma@microsoft.com>
- Date: Wed, 15 Dec 2010 07:19:17 +0000
- To: "public-web-perf@w3.org" <public-web-perf@w3.org>
- Message-ID: <F677C405AAD11B45963EEAE5202813BD02894C09@TK5EX14MBXW651.wingroup.windeploy.ntde>
We have submitted a few additional test cases for NavigationTiming: http://test.w3.org/webperf/tests/submission/Microsoft/NavigationTiming/ These tests use the testharness.js provided in the resources folder, so they should perform similarly to Zhiheng's test case. I tried to add a short description and setup steps at the top of the page. These tests are very simple: * mstestharness.js: Helper functions used by several of the tests * test_navigation_attributes_exist.htm: Checks the existence of performance.navigation attributes * test_navigation_redirectCount_none.htm: Checks the redirectCount and redirectStart/redirectEnd in the case of a non-redirected navigation * test_navigation_type_enums.htm: Checks the existence and values of navigation.type enums * test_navigation_type_reload.htm: Has the user hit Reload and checks navigation.type * test_timing_attributes_exist.htm: Checks the existence of performance.timing attributes * test_timing_attributes_ordering_simple.htm: Instructs the user how to start the test (click a link) * test_timing_attributes_ordering_simple_test.htm: Checks the values (ordering) of the timing attributes, during the page load and during/after the onload event handler * test_timing_unloadEvent.htm: Instructs the user how to start the test (click a link) * test_timing_unloadEvent_test.htm: Checks the value of the unloadEventStart/End coming from a previous page on the same domain These tests are by no means exhaustive or complete. Looking forward to any feedback on the style and approach! - Nic
Received on Wednesday, 15 December 2010 07:19:55 UTC