Closed
Bug 381633
Opened 17 years ago
Closed 17 years ago
xpcshell test harness should use strict warnings in JavaScript
Categories
(Testing :: XPCShell Harness, defect)
Testing
XPCShell Harness
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sdwilsh, Assigned: sdwilsh)
Details
Attachments
(1 file)
|
980 bytes,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
I spent several hours today and yesterday trying to fix orange (which we ended up just commenting out the tests) for something that would have easily been found with strict warnings enabled. It's really easy to fix, and could be a big help for people debugging their tests.
Attachment #265706 -
Flags: review?(rcampbell)
|
Assignee | |
Updated•17 years ago
|
Assignee: nobody → sdwilsh
|
||
Updated•17 years ago
|
Attachment #265706 -
Flags: review?(rcampbell) → review+
|
|
Assignee | |
Comment 1•17 years ago
|
||
Checking in tools/test-harness/xpcshell-simple/test_all.sh; new revision: 1.9; previous revision: 1.8
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
|
||
Updated•16 years ago
|
Component: Testing → TUnit
Product: Core → Testing
QA Contact: testing → tunit
You need to log in
before you can comment on or make changes to this bug.
Description
•