Closed
Bug 692987
Opened 13 years ago
Closed 13 years ago
Run xpcshell tests with JSD debugging active
Categories
(Testing :: XPCShell Harness, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla11
People
(Reporter: sfink, Assigned: sfink)
References
Details
Attachments
(1 file)
(deleted),
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
Over in bug 692722, I'm trying to add a '-d' flag to xpcshell to run tests with JSD on. You can't turn it on from the test script, because you can only turn it on when no JS is on the stack. With an xpcshell test, there's always JS on the stack (running a nested event loop isn't good enough.)
This bug is for adding support the xpcshell test manifests to request that a given test be run with -d. I'll be posting a sample test to bug 689101 in a second.
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #565682 -
Flags: review?(ted.mielczarek)
Comment 2•13 years ago
|
||
Comment on attachment 565682 [details] [diff] [review]
add manifest option to add -d to xpcshell command line
Review of attachment 565682 [details] [diff] [review]:
-----------------------------------------------------------------
Looks useful! Two things:
1) Make sure you document this somewhere on MDN!
2) Is it possible to write a little sanity test for this in http://mxr.mozilla.org/mozilla-central/source/testing/xpcshell/example/unit/ ? (I'm not sure what enabling JSD actually exposes to your tests.)
Attachment #565682 -
Flags: review?(ted.mielczarek) → review+
Updated•13 years ago
|
Assignee: nobody → sphink
Comment 3•13 years ago
|
||
backed out bug 689101, bug 692987 and bug 692722, since one of these caused permaorange on OSX64 m-oth tests (bug 692605 went permaorange on inbound, exactly)
Assignee | ||
Comment 4•13 years ago
|
||
trying again. Looked good on try: https://tbpl.mozilla.org/?tree=Try&rev=51ba3fc4f12f
https://hg.mozilla.org/integration/mozilla-inbound/rev/4e829c32aa12
Target Milestone: --- → mozilla11
Comment 5•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•