node/test/fixtures/wpt/user-timing/measures.html
legendecas 062f8e3730
perf_hooks: web performance timeline compliance
All API introduced in this PR are compliant with web
[performance-timeline](https://w3c.github.io/performance-timeline)
spec. "performance-timeline" is listed as supported web spec in the doc
https://nodejs.org/docs/latest/api/perf_hooks.html#perf_hooks_performance_measurement_apis.

Changes summary:
1. Add new supported wpt test subsets: user-timing and
  performance-timeline.
2. Add support for `Performance.getEntries`,
  `Performance.getEntriesByName` and `Performance.getEntriesByType`
  to synchronously fetch buffered performance entries. This means
  the user should invoke `Performance.clearMarks` and
  `Performance.clearMeasures` to clear buffered entries to prevent from
  those entries been kept alive forever.
3. Add support (again after https://github.com/nodejs/node/pull/37136)
  for `buffered` flags for `PerformanceObserver`.
3. Fixes `PerformanceMark` and `PerformanceMeasure` wpt compliance
  issues.
4. Only user-created performance entries will be buffered globally. This
  behavior should be compliant with
  https://w3c.github.io/timing-entrytypes-registry/#registry.

With the new ability to fetch user-created performance entries
synchronously, the issues raised in
https://github.com/nodejs/diagnostics/issues/464#issuecomment-861920116
could also be fixed.

PR-URL: https://github.com/nodejs/node/pull/39297
Reviewed-By: James M Snell <jasnell@gmail.com>
2021-07-25 23:43:31 +08:00

66 lines
2.6 KiB
HTML

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title>functionality test of window.performance.measure</title>
<link rel="author" title="Intel" href="http://www.intel.com/" />
<link rel="help" href="http://www.w3.org/TR/user-timing/#extensions-performance-interface"/>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="/common/performance-timeline-utils.js"></script>
<script src="resources/webperftestharness.js"></script>
<script src="resources/webperftestharnessextension.js"></script>
<script>
setup({ explicit_done: true });
function onload_test()
{
const context = new PerformanceContext(window.performance);
const entrylist_checker = new performance_entrylist_checker('measure');
const measure_names = measures.map(function(x) {return x[0];});
test_equals(context.getEntriesByType('measure').length, 0, 'There should be ' + 0 + ' entries returned.');
mark_names.forEach(function(name) {
context.mark(name);
});
measures.forEach(context.initialMeasures, context);
let measure_entrylist = context.getEntriesByType('measure');
entrylist_checker.entrylist_check(measure_entrylist, measures.length, measure_names,
'Checking all entries.');
for (let i = 0; i < measure_entrylist.length; ++i)
{
const measure_entrylist_by_name = context.getEntriesByName(measure_entrylist[i].name, 'measure');
entrylist_checker.entrylist_check(measure_entrylist_by_name, 1, measure_names,
'First loop: checking entry of name "' + measure_entrylist[i].name + '".');
}
// Following cases test for scenarios that measure names are tied for two times
mark_names.forEach(function(name) {
context.mark(name);
});
measures.forEach(context.initialMeasures, context);
measure_entrylist = context.getEntriesByType('measure');
entrylist_checker.entrylist_check(measure_entrylist, measures.length * 2, measure_names,
'Checking all doubly measured entries.');
for (let i = 0; i < measure_entrylist.length; ++i)
{
const measure_entrylist_by_name = context.getEntriesByName(measure_entrylist[i].name, 'measure');
entrylist_checker.entrylist_check(measure_entrylist_by_name, 2, measure_names,
'Second loop step ' + i + ': checking entry of name "' + measure_entrylist[i].name + '".');
}
done();
}
</script>
</head>
<body onload=onload_test()>
<h1>Description</h1>
<p>This test validates functionality of the interface window.performance.measure.</p>
<div id="log"></div>
</body>
</html>