Regarding the test cases of course the most useful bug reports are ones with a small test case isolating the problem. These usually mean we can find and fix the problem in a few hours. As a result these cases get priority.
Large test cases with a clear step-by-step reproduction are helpful. But it usually means we need to plan on a day to reduce the problem to a smaller case. Attached test files are best. Online URLs are a bit like large test cases: we have to analyze them to create a local test case. Reports without test cases are essentially the same as posting to this newsgroup. They allow us to make suggestions on things to try and they encourage other users to note similar cases that work/fail for them. I mark the issues either "needTestcase" or "testcase" when I first read them. I consider the list of outstanding bugs needing work to be the 'testcase' list. So currently we have 135 bugs, a bit high as happens just before we start a new version. See https://wiki.mozilla.org/Firebug/MarchOfTheFirebugs As for 1504, it already has a user reporting that under similar conditions they don't see the problem you have. Hopefully this kind of information will narrow the problem down. jjb On Feb 18, 8:36 am, Robert Kieffer <[email protected]> wrote: > Hi John, my apologies if my original post came across as whining or as > a rant. 'Certainly didn't intend it to be such. Rather, there was > just a general sense among my team here with how unreliable has been > for us Firebug was for our team and I wanted to see what suggestions > this community might have to help address the problem. > > As you guessed, the 1.3.3b3 release proved to be of little help. > However, the suggestion of testing with a new profile was certainly > useful. With it we were able to isolate at least one of the problem > as being related to having the Web Developer addon installed. I've > filed a bug report here:http://code.google.com/p/fbug/issues/detail?id=1504 > > ... which brings me to another question. I certainly appreciate how > useful concrete bug reports are but can you comment on whether or not > a report like the one above is actually useful to you? I was unable > to isolate the problem to a standalone test case and, instead, am > forced to provide a recipe that just referes to a page on our > website. Unfortunately I can't make any guarantees as to how long > that page will be useful as a resource in reproducing this bug, which > has me wondering if I should have even bothered... :-P > > (That said, this is a "Firefox crasher" bug, so I'm hoping it'll get > some attention ASAP. :) ) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
