gecko-dev/testing/mochitest/tests/browser/browser_fail_async.js
Paolo Amadini a002e5d1d1 Bug 1365649 - Improve browser-chrome self-tests and the "fail-if" manifest property handling. r=Mossop
The browser-chrome self-test files now use the setExpectedFailuresForSelfTest function to specify the exact number of assertion failures that will be triggered. Also, most failures are now intercepted when specifying the "fail-if" property in a "browser.ini" manifest, while previously only those triggered using the "ok" function were intercepted. This allows re-enabling several browser-chome self-tests.

MozReview-Commit-ID: DlDjWaJPfvH

--HG--
extra : rebase_source : d9977dac6ecbd2b28f5697d22ce6edf4e1d4f899
extra : source : 6da58c7bb247d3e879012bea8d848eb68f16e36e
2017-05-27 09:12:02 +01:00

10 lines
148 B
JavaScript

setExpectedFailuresForSelfTest(1);
function test() {
waitForExplicitFinish();
executeSoon(() => {
ok(false, "fail");
finish();
});
}