Bug 940637 - part 2 - update TestRunner.js to understand new dumping options; r=jmaher

This commit is contained in:
Nathan Froyd 2013-11-21 13:02:56 -05:00
parent 7f4310a1ba
commit fadbe0d0c9
2 changed files with 16 additions and 0 deletions

View File

@ -1,3 +1,4 @@
/* -*- js-indent-level: 4 -*- */
/*
* e10s event dispatcher from content->chrome
*
@ -84,6 +85,9 @@ TestRunner._expectedMaxAsserts = 0;
TestRunner.timeout = 5 * 60 * 1000; // 5 minutes.
TestRunner.maxTimeouts = 4; // halt testing after too many timeouts
TestRunner.runSlower = false;
TestRunner.dumpOutputDirectory = "";
TestRunner.dumpAboutMemoryAfterTest = false;
TestRunner.dumpDMDAfterTest = false;
TestRunner.slowestTestTime = 0;
TestRunner.slowestTestURL = "";

View File

@ -131,6 +131,18 @@ if (params.runSlower) {
TestRunner.runSlower = true;
}
if (params.dumpOutputDirectory) {
TestRunner.dumpOutputDirectory = params.dumpOutputDirectory;
}
if (params.dumpAboutMemoryAfterTest) {
TestRunner.dumpAboutMemoryAfterTest = true;
}
if (params.dumpDMDAfterTest) {
TestRunner.dumpDMDAfterTest = true;
}
var gTestList = [];
var RunSet = {}
RunSet.runall = function(e) {