gecko-dev/devtools/server/tests/browser/browser_perf-allocation-data.js
yulia 1174ad2f82 Bug 1495389 - adjust test to use new performance front initialization; r=ochameau
Depends on D10564

Differential Revision: https://phabricator.services.mozilla.com/D11293

--HG--
extra : moz-landing-system : lando
2018-12-17 11:54:45 +00:00

33 lines
1.1 KiB
JavaScript

/* Any copyright is dedicated to the Public Domain.
http://creativecommons.org/publicdomain/zero/1.0/ */
/**
* Test that we have allocation data coming from the front.
*/
"use strict";
add_task(async function() {
const target = await addTabTarget(MAIN_DOMAIN + "doc_allocations.html");
const front = await target.getFront("performance");
const rec = await front.startRecording(
{ withMarkers: true, withAllocations: true, withTicks: true });
await waitUntil(() => rec.getAllocations().frames.length);
await waitUntil(() => rec.getAllocations().timestamps.length);
await waitUntil(() => rec.getAllocations().sizes.length);
await waitUntil(() => rec.getAllocations().sites.length);
await front.stopRecording(rec);
const { timestamps, sizes } = rec.getAllocations();
is(timestamps.length, sizes.length, "we have the same amount of timestamps and sizes");
ok(timestamps.every(time => time > 0 && typeof time === "number"),
"all timestamps have numeric values");
ok(sizes.every(n => n > 0 && typeof n === "number"), "all sizes are positive numbers");
await target.destroy();
gBrowser.removeCurrentTab();
});