Open Bug 412109 Opened 14 years ago Updated 1 year ago
TB xpcom null arg test suite, mostly to make it harder for extension authors to shoot themselves in the foot
Inspired by bug 411646, this is a test-suite for a global check to make sure all of tb's xpcom components and functions handle null arguments gracefully (ie. don't crash). Bugs blocking this one are those which this test uncovered, since we can't enable it until they're fixed. The test does have a known-failures option if a few turn out to be especially pesky. Meant to be run from xpcshell. I'll hook it into the normal |make check| routine as we get closer to enabling it.
I should add that while we may catch a few live crashers in these tests, the vast majority of this is simply making it harder for extension authors to shoot themselves in the foot.
This is the same test-suite, but with all the known failures not fixed by the blocking bugs. There's still a shutdown crash that I haven't figured out yet though, if someone wants to poke at that.
Attachment #296744 - Attachment is obsolete: true
I was ping'ed in bug 413548, I looked at this bug and related ones. Joey's patches are nearly 3-year old and spread in multiple bugs, which confuses me a little, (I'll refer to them yet), then I prefer to probably do more but one file at a time, as in bug 611233.
Version: unspecified → Trunk
Serge, when the blocking bugs will get closed, are you able to use the attached testsuite and check if everything got fixed? If yes, then you could take this bug.
Assignee: jminta → nobody
Status: ASSIGNED → NEW
Component: General → Backend
Product: Thunderbird → MailNews Core
QA Contact: general → backend
Summary: TB xpcom null arg test suite → TB xpcom null arg test suite, mostly to make it harder for extension authors to shoot themselves in the foot.
You need to log in before you can comment on or make changes to this bug.