Open
Bug 906232
Opened 11 years ago
Updated 2 years ago
Remove all "diagnostic messages" from xpcshell tests
Categories
(Testing :: XPCShell Harness, task, P5)
Testing
XPCShell Harness
Tracking
(Not tracked)
NEW
People
(Reporter: fitzgen, Unassigned)
References
(Blocks 1 open bug)
Details
I have been adding strings for what each assertion is testing (eg, do_check_true(foo, "message")). Turns out that I've been doing it wrong and that parameter is actually for a stack that you can pass in to say where the error came from. This overrides the normal stack, so we lose location information about which error is failing. Woops!
Reporter | ||
Updated•11 years ago
|
OS: Mac OS X → All
Priority: -- → P3
Hardware: x86 → All
Comment 1•11 years ago
|
||
The xpcshell harness is kind of dumb, this doesn't match what every other test harness in the world does. Maybe we should just fix the harness to have a description parameter, and shift stack back one? I can't imagine anyone is actually passing in a stack there (aside from the harness itself).
Comment 2•10 years ago
|
||
Fixing the harness seems like the right thing to do. Bobby, what do you think we should do here?
Flags: needinfo?(bobbyholley)
Comment 3•10 years ago
|
||
I agree that we should just fix the harness, but it's kind of irrelevant because this is a bug in the harness which ted owns (not I).
Flags: needinfo?(bobbyholley)
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 4•5 years ago
|
||
Nick, Bobby is this still relevant? Also what is the right bugzilla component for it if it is?
Type: defect → task
Priority: P3 → P5
Comment 5•5 years ago
|
||
(In reply to Jason Laster [:jlast] from comment #4)
Nick, Bobby is this still relevant? Also what is the right bugzilla component for it if it is?
May or may not be relevant, moving it to the right component.
Component: Debugger → XPCShell Harness
Product: DevTools → Testing
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•