gecko-dev/devtools/server/tests/browser/browser_perf-04.js
Nazım Can Altınova e88550b119 Bug 1476775 - Part 2: Change the profiler usage in devtools after API change r=julienw,gregtatum
Depends on D6267

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

--HG--
extra : moz-landing-system : lando
2018-11-23 16:10:08 +00:00

37 lines
1.3 KiB
JavaScript

/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
"use strict";
/**
* Run through a series of basic recording actions for the perf actor.
*/
add_task(async function() {
const {front, client} = await initPerfFront();
// Assert the initial state.
is(await front.isSupportedPlatform(), true,
"This test only runs on supported platforms.");
is(await front.isLockedForPrivateBrowsing(), false,
"The browser is not in private browsing mode.");
is(await front.isActive(), false,
"The profiler is not active yet.");
front.once("profiler-started", (entries, interval, features, duration) => {
is(entries, 1000, "Should apply entries by startProfiler");
is(interval, 0.1, "Should apply interval by startProfiler");
is(features, 0x202, "Should apply features by startProfiler");
is(duration, 2, "Should apply duration by startProfiler");
});
// Start the profiler.
await front.startProfiler({ entries: 1000, duration: 2, interval: 0.1,
features: ["js", "stackwalk"] });
is(await front.isActive(), true, "The profiler is active.");
// clean up
await front.stopProfilerAndDiscardProfile();
await front.destroy();
await client.close();
});