Bug 1476526 - Make browser-chrome baseline test use functions from BrowserTestUtils. r?marco
In this patch, the browser-chrome (or `.js`) baseline test is made to use functions from BrowserTestUtils so that they are ignored in per-test coverage data.
MozReview-Commit-ID: 5QLg05w5xLt
--- a/testing/mochitest/baselinecoverage/browser_chrome/browser_baselinecoverage.js
+++ b/testing/mochitest/baselinecoverage/browser_chrome/browser_baselinecoverage.js
@@ -3,11 +3,20 @@
/* eslint-disable mozilla/no-arbitrary-setTimeout */
"use strict";
const { setTimeout } = ChromeUtils.import("resource://gre/modules/Timer.jsm", {});
add_task(async function() {
requestLongerTimeout(2);
- ok(true, "Collecting baseline coverage for javascript (.js) file types.");
- await new Promise((c) => setTimeout(c, 30 * 1000));
+ let newWin = await BrowserTestUtils.openNewBrowserWindow();
+
+ await BrowserTestUtils.withNewTab({
+ gBrowser,
+ url: "about:blank"
+ }, async function(browser) {
+ ok(true, "Collecting baseline coverage for javascript (.js) file types.");
+ await new Promise((c) => setTimeout(c, 30 * 1000));
+ });
+
+ await BrowserTestUtils.closeWindow(newWin);
});