gecko/mobile/android/base/tests/robocop_testharness.js
Jim Blandy 4d6a633bba Bug 914753: Make Emacs file variable header lines correct, or at least consistent. DONTBUILD r=ehsan
The -*- file variable lines -*- establish per-file settings that Emacs will
pick up. This patch makes the following changes to those lines (and touches
nothing else):

 - Never set the buffer's mode.

   Years ago, Emacs did not have a good JavaScript mode, so it made sense
   to use Java or C++ mode in .js files. However, Emacs has had js-mode for
   years now; it's perfectly serviceable, and is available and enabled by
   default in all major Emacs packagings.

   Selecting a mode in the -*- file variable line -*- is almost always the
   wrong thing to do anyway. It overrides Emacs's default choice, which is
   (now) reasonable; and even worse, it overrides settings the user might
   have made in their '.emacs' file for that file extension. It's only
   useful when there's something specific about that particular file that
   makes a particular mode appropriate.

 - Correctly propagate settings that establish the correct indentation
   level for this file: c-basic-offset and js2-basic-offset should be
   js-indent-level. Whatever value they're given should be preserved;
   different parts of our tree use different indentation styles.

 - We don't use tabs in Mozilla JS code. Always set indent-tabs-mode: nil.
   Remove tab-width: settings, at least in files that don't contain tab
   characters.

 - Remove js2-mode settings that belong in the user's .emacs file, like
   js2-skip-preprocessor-directives.
2014-06-24 22:12:07 -07:00

71 lines
2.6 KiB
JavaScript

// -*- indent-tabs-mode: nil; js-indent-level: 2 -*-
/* 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/. */
function sendMessageToJava(message) {
SpecialPowers.Services.androidBridge.handleGeckoMessage(message);
}
function _evalURI(uri, sandbox) {
// We explicitly allow Cross-Origin requests, since it is useful for
// testing, but we allow relative URLs by maintaining our baseURI.
let req = SpecialPowers.Cc["@mozilla.org/xmlextras/xmlhttprequest;1"]
.createInstance();
let baseURI = SpecialPowers.Services.io
.newURI(window.document.baseURI, window.document.characterSet, null);
let theURI = SpecialPowers.Services.io
.newURI(uri, window.document.characterSet, baseURI);
req.open('GET', theURI.spec, false);
req.send();
return SpecialPowers.Cu.evalInSandbox(req.responseText, sandbox, "1.8", uri, 1);
}
/**
* Execute the Javascript file at `uri` in a testing sandbox populated
* with the Javascript test harness.
*
* `uri` should be a String, relative (to window.document.baseURI) or
* absolute.
*
* The Javascript test harness sends all output to Java via
* Robocop:JS messages.
*/
function testOneFile(uri) {
let HEAD_JS = "robocop_head.js";
// System principal. This is dangerous, but this is test code that
// should only run on developer and build farm machines, and the
// test harness needs access to a lot of the Components API,
// including Components.stack. Wrapping Components.stack in
// SpecialPowers magic obfuscates stack traces wonderfully,
// defeating much of the point of the test harness.
let principal = SpecialPowers.Cc["@mozilla.org/systemprincipal;1"]
.createInstance(SpecialPowers.Ci.nsIPrincipal);
let testScope = SpecialPowers.Cu.Sandbox(principal);
// Populate test environment with test harness prerequisites.
testScope.Components = SpecialPowers.Components;
testScope._TEST_FILE = uri;
// Output from head.js is fed, line by line, to this function. We
// send any such output back to the Java Robocop harness.
testScope.dump = function (str) {
let message = { type: "Robocop:JS",
innerType: "progress",
message: str,
};
sendMessageToJava(message);
};
// Populate test environment with test harness. The symbols defined
// above must be present before executing the test harness.
_evalURI(HEAD_JS, testScope);
return _evalURI(uri, testScope);
}