Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(185)

Unified Diff: LayoutTests/http/tests/w3c/webperf/approved/UserTiming/test_user_timing_measure_navigation_timing-expected.txt

Issue 1191043004: Import hr-time and user-timing tests, remove redundant webperf copies (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Add idlharness result Created 5 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: LayoutTests/http/tests/w3c/webperf/approved/UserTiming/test_user_timing_measure_navigation_timing-expected.txt
diff --git a/LayoutTests/http/tests/w3c/webperf/approved/UserTiming/test_user_timing_measure_navigation_timing-expected.txt b/LayoutTests/http/tests/w3c/webperf/approved/UserTiming/test_user_timing_measure_navigation_timing-expected.txt
deleted file mode 100644
index ec0270b063556bab6f7be156e9da93bb6e2a4120..0000000000000000000000000000000000000000
--- a/LayoutTests/http/tests/w3c/webperf/approved/UserTiming/test_user_timing_measure_navigation_timing-expected.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-Description
-
-This test validates that the performance.measure() method is working properly when navigation timing attributes are used in place of mark names. This test creates the following measures to test this method:
-
-"measure_nav_start_no_end": created using a measure() call with a navigation timing attribute provided as the startMark and nothing provided as the endMark
-"measure_nav_start_mark_end": created using a measure() call with a navigation timing attribute provided as the startMark and a mark name provided as the endMark
-"measure_mark_start_nav_end": created using a measure() call with a mark name provided as the startMark and a navigation timing attribute provided as the endMark
-"measure_nav_start_nav_end":created using a measure() call with a navigation timing attribute provided as both the startMark and endMark
-After creating each measure, the existence of these measures is validated by calling performance.getEntriesByName() with each measure name
-
-PASS window.performance is defined
-PASS window.performance.getEntriesByName("measure_nav_start_no_end")[0].name == "measure_nav_start_no_end"
-PASS window.performance.getEntriesByName("measure_nav_start_no_end")[0].startTime ==
-PASS window.performance.getEntriesByName("measure_nav_start_no_end")[0].entryType == "measure"
-PASS window.performance.getEntriesByName("measure_nav_start_no_end")[0].duration ~== (up to 20ms difference allowed)
-PASS window.performance.getEntriesByName("measure_nav_start_mark_end")[0].name == "measure_nav_start_mark_end"
-PASS window.performance.getEntriesByName("measure_nav_start_mark_end")[0].startTime ==
-PASS window.performance.getEntriesByName("measure_nav_start_mark_end")[0].entryType == "measure"
-PASS window.performance.getEntriesByName("measure_nav_start_mark_end")[0].duration ~== (up to 20ms difference allowed)
-PASS window.performance.getEntriesByName("measure_mark_start_nav_end")[0].name == "measure_mark_start_nav_end"
-PASS window.performance.getEntriesByName("measure_mark_start_nav_end")[0].startTime ==
-PASS window.performance.getEntriesByName("measure_mark_start_nav_end")[0].entryType == "measure"
-PASS window.performance.getEntriesByName("measure_mark_start_nav_end")[0].duration ~== (up to 20ms difference allowed)
-PASS window.performance.getEntriesByName("measure_nav_start_nav_end")[0].name == "measure_nav_start_nav_end"
-PASS window.performance.getEntriesByName("measure_nav_start_nav_end")[0].startTime ==
-PASS window.performance.getEntriesByName("measure_nav_start_nav_end")[0].entryType == "measure"
-PASS window.performance.getEntriesByName("measure_nav_start_nav_end")[0].duration ~== (up to 20ms difference allowed)
-

Powered by Google App Engine
This is Rietveld 408576698