Open
Bug 603234
Opened 14 years ago
Updated 2 years ago
chrome-harness.js: code issue, documentation nits
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
NEW
People
(Reporter: sgautherie, Unassigned)
References
()
Details
By chance, I noticed an indentation/brackets issue at lineq 215 vs 217:
{
213 // If we were passed a speComponents.interfacesfic file, run only that test.
214 if (testsDir.isFile()) {
215 if (fileNameRegexp.test(testsDir.leafName))
216 var singlePath = basePath + '/' + testPath;
217 var links = {};
218 links[singlePath] = true;
219 return [links, singlePath];
220
221 // We were passed a file that's not a test...
222 return [];
223 }
}
I also wonder what "speComponents.interfacesfic" means.
Same with "aComponents.classesess" at
{
184 * srvScope: loaded javascript to server.js so we have aComponents.classesess to the list() function
}
Reporter | ||
Updated•14 years ago
|
Summary: "chrome-harness.js:112 / variable basePath redeclares argument" → chrome-harness.js: code issue, documentation nits
Assignee | ||
Updated•7 years ago
|
Component: Mochitest Chrome → Mochitest
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•